When attempting to add a column to a datasource with a live connection, sometimes it will throw this error:
Metadata does not exist
This happens because added/updated columns will have the metadata enforced. When updating metadata for a datasource with an extract, there are two sections where metadata is stored and updated - the connection and the extract connection. However, live connections typically do not have any extract connection metadata, which is why this error appears for live connections. If this error does not happen for a live connection, it is because that extract metadata is lingering from an old extract connection.
Changes
Updated the 'Metadata does not exist' error to only appear for datasource-metadata
Datasources with either extract or live connections should have datasource-metadata, so if it is not found, it should throw an error
If extract-metadata is missing, it will be skipped without an error
It is expected that live connections should not have extract-metadata
Tests
[x] Tested locally on a datasource know to give this error
datasource-metadata was updated
[x] Tested locally on a datasource that did not give this error
Summary
When attempting to add a column to a datasource with a live connection, sometimes it will throw this error:
This happens because added/updated columns will have the metadata enforced. When updating metadata for a datasource with an extract, there are two sections where metadata is stored and updated - the connection and the extract connection. However, live connections typically do not have any extract connection metadata, which is why this error appears for live connections. If this error does not happen for a live connection, it is because that extract metadata is lingering from an old extract connection.
Changes
datasource-metadataextractorliveconnections should havedatasource-metadata, so if it is not found, it should throw an errorextract-metadatais missing, it will be skipped without an errorextract-metadataTests