GitHub user Dhruvin4530 created a discussion: Error while exporting datasources in superset version 2.1.0
superset export-datasources -f datasources_export.zip Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py] logging was configured successfully 2025-10-03 14:16:12,848:INFO:superset.utils.logging_configurator:logging was configured successfully 2025-10-03 14:16:12,852:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'> We haven't found any Content Security Policy (CSP) defined in the configurations. Please make sure to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any other external software. Failing to configure CSP have serious security implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for more information. You can disable this warning using the CONTENT_SECURITY_POLICY_WARNING key. 2025-10-03 14:16:12,852:WARNING:superset.initialization:We haven't found any Content Security Policy (CSP) defined in the configurations. Please make sure to configure CSP using the TALISMAN_ENABLED and TALISMAN_CONFIG keys or any other external software. Failing to configure CSP have serious security implications. Check https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP for more information. You can disable this warning using the CONTENT_SECURITY_POLICY_WARNING key. /usr/local/lib/python3.8/site-packages/flask_appbuilder/models/sqla/interface.py:67: SAWarning: relationship 'SqlaTable.slices' will copy column tables.id to column slices.datasource_id, which conflicts with relationship(s): 'Slice.table' (copies tables.id to slices.datasource_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards. To silence this warning, add the parameter 'overlaps="table"' to the 'SqlaTable.slices' relationship. (Background on this error at: https://sqlalche.me/e/14/qzyx) for prop in class_mapper(obj).iterate_properties: There was an error when exporting the datasets, please check the exception traceback in the log Traceback (most recent call last): File "/app/superset/cli/importexport.py", line 122, in export_datasources for file_name, file_content in ExportDatasetsCommand(dataset_ids).run(): File "/app/superset/commands/export/models.py", line 49, in run self.validate() File "/app/superset/commands/export/models.py", line 68, in validate raise self.not_found() superset.datasets.commands.exceptions.DatasetNotFoundError: Dataset does not exist 2025-10-03 14:16:14,873:ERROR:superset.cli.importexport:There was an error when exporting the datasets, please check the exception traceback in the log Traceback (most recent call last): File "/app/superset/cli/importexport.py", line 122, in export_datasources for file_name, file_content in ExportDatasetsCommand(dataset_ids).run(): File "/app/superset/commands/export/models.py", line 49, in run self.validate() File "/app/superset/commands/export/models.py", line 68, in validate raise self.not_found() superset.datasets.commands.exceptions.DatasetNotFoundError: Dataset does not exist GitHub link: https://github.com/apache/superset/discussions/35483 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
