You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to import a CSV dataset via the superset API with the endpoint /api/v1/dataset/import/, the request response is {"message": "OK"}, which indicates that everything went well.
The problem is that the dataset has not been imported, and the following messages appear in the logs:
/app/superset/commands/importers/v1/utils.py:113: SAWarning: TypeDecorator EncryptedType() will not produce a cache key because the ``cache_ok`` attribute is not set to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Set this attribute to True if this type object's state is safe to use in a cache key, or False to disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)
for uuid, password in db.session.query(Database.uuid, Database.password).all()
/app/superset/commands/importers/v1/utils.py:118: SAWarning: TypeDecorator EncryptedType() will not produce a cache key because the ``cache_ok`` attribute is not set to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Set this attribute to True if this type object's state is safe to use in a cache key, or False to disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)
for uuid, password in db.session.query(SSHTunnel.uuid, SSHTunnel.password).all()
/app/superset/commands/importers/v1/utils.py:125: SAWarning: TypeDecorator EncryptedType() will not produce a cache key because the ``cache_ok`` attribute is not set to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Set this attribute to True if this type object's state is safe to use in a cache key, or False to disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)
).all()
/app/superset/commands/importers/v1/utils.py:132: SAWarning: TypeDecorator EncryptedType() will not produce a cache key because the ``cache_ok`` attribute is not set to True. This can have significant performance implications including some performance degradations in comparison to prior SQLAlchemy versions. Set this attribute to True if this type object's state is safe to use in a cache key, or False to disable this warning. (Background on this error at: https://sqlalche.me/e/14/cprf)
).all()
I'm importing without using an SSH tunnel. Is the use of an SSH tunnel mandatory? If not, how can I fix this problem?
Thank you in advance for your help.
How to reproduce the bug
Call endpoint /api/v1/dataset/import/ with parameters formData and passwords. Not use the ssh tunnel informations
One authenticated, add the bearer token and the csrf token, then launch the test
You will receive {"message": "OK"} even if the dataset is not imported
Hey @kdaouda 👋, I'm here to help you with your Superset issue. I'm a bot that can assist you with bugs, questions, and becoming a contributor. Let's squash this bug together! 🤖
To fix the issue where the Superset API endpoint /api/v1/dataset/import/ returns {"message": "OK"} but does not actually import the dataset, and the logs show warnings related to TypeDecorator EncryptedType(), you should ensure that the ImportDatasetsCommand is correctly processing the dataset contents and handling any encryption-related issues.
Here is a possible solution to add error handling and logging to the ImportDatasetsCommand execution:
Additionally, ensure that the encryption configuration is correctly set up in your application. The EncryptedType requires a SECRET_KEY to be specified in the app configuration. Here is an example of how the encryption setup should be initialized:
Make sure that the SECRET_KEY is correctly set in your application configuration. This key is essential for the EncryptedType to function properly. If the SECRET_KEY is missing or incorrect, it could lead to issues with the encryption and decryption processes, which might be causing the dataset import to fail silently [1][2][3][4].
Bug description
Hi everyone,
I need your help.
When I try to import a CSV dataset via the superset API with the endpoint /api/v1/dataset/import/, the request response is {"message": "OK"}, which indicates that everything went well.
The problem is that the dataset has not been imported, and the following messages appear in the logs:
I'm importing without using an SSH tunnel. Is the use of an SSH tunnel mandatory? If not, how can I fix this problem?
Thank you in advance for your help.
How to reproduce the bug
/api/v1/dataset/import/
with parametersformData
andpasswords
. Not use the ssh tunnel informationsScreenshots/recordings
example_import_dataset_superset.zip
Superset version
4.0.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: