For some tables, the metadata cannot be downloaded, even if it is visible in the metadata widget (on the ‘Meta information’ tab on the table details page).
Some time ago, we introduced a new approach to storing metadata. Previously, metadata was stored as an SQL comment to a table. Now the metadata is stored in the database (internal to django).
The metadata view (api) provides the GET method to retrieve the metadata, but the code still fetches the metadata from the comment-on table. We still store it there as we have decided to keep the bot memory for some time. In some cases (when no cursor is passed) the metadata is not stored as a comment in the table. This leads to the current problem.
We always have to retrieve the metadata from the database.
Description of the issue
For some tables, the metadata cannot be downloaded, even if it is visible in the metadata widget (on the ‘Meta information’ tab on the table details page).
Steps to Reproduce
Ideas of solution
Some time ago, we introduced a new approach to storing metadata. Previously, metadata was stored as an SQL comment to a table. Now the metadata is stored in the database (internal to django).
The metadata view (api) provides the GET method to retrieve the metadata, but the code still fetches the metadata from the comment-on table. We still store it there as we have decided to keep the bot memory for some time. In some cases (when no cursor is passed) the metadata is not stored as a comment in the table. This leads to the current problem.
We always have to retrieve the metadata from the database.
Context and Environment
Workflow checklist