When adding a new source in the configuration tab, a user can specify the connection details and cdm/results/temp/vocab schemas. For every data source there is a check feature. When using the check feature, I erroneously assumed a validation for those specified cdm/results/temp/vocab schemas existing in the database was being performed.
Actual behavior
The check feature only validates that the database connection itself is valid.
Request
A nice expansion of the check feature could be to verify that the user specified schemas exist in the database and report if they do not exist to the user. This would be very useful when a single database contains several data sources (with a collection of schemas) that need to be made available in Atlas and you want to verify that the new schema(s) associated with the new data source exist(s) prior to making it available for users.
Expected behavior
When adding a new source in the configuration tab, a user can specify the connection details and cdm/results/temp/vocab schemas. For every data source there is a
checkfeature. When using thecheckfeature, I erroneously assumed a validation for those specified cdm/results/temp/vocab schemas existing in the database was being performed.Actual behavior
The
checkfeature only validates that the database connection itself is valid.Request
A nice expansion of the
checkfeature could be to verify that the user specified schemas exist in the database and report if they do not exist to the user. This would be very useful when a single database contains several data sources (with a collection of schemas) that need to be made available in Atlas and you want to verify that the new schema(s) associated with the new data source exist(s) prior to making it available for users.