Open bmtcril opened 7 months ago
@rusackas We have experienced this issue in two different Superset installations. Our MySQL version is 8.1.0
We're experiencing the same issue using Postgres 16.1 on superset 4.0.X
We are also experiencing the same issue. Is there any workaround apart from turning off the TAGGING_SYSTEM feature flag?
I was able to fix it after commenting below lines in superset/tags/core.py
file.
sqla.event.listen(SqlaTable, "after_insert", DatasetUpdater.after_insert)
sqla.event.listen(SqlaTable, "after_update", DatasetUpdater.after_update)
sqla.event.listen(SqlaTable, "after_delete", DatasetUpdater.after_delete)
Bug description
When importing a dataset on the command line we consistently run into the error as described in #24528 . The problem seems to be that
dataset
isn't included in the enum on thetaggable_objects
table. So far the only workaround has been to turn off theTAGGING_SYSTEM
feature flag.How to reproduce the bug
superset.examples.utils.load_configs_from_directory
MySQLdb._exceptions.DataError: (1265, "Data truncated for column 'object_type' at row 1")
Screenshots/recordings
No response
Superset version
4.0.0
Python version
3.9
Node version
16
Browser
Not applicable
Additional context
Note the attempt to insert "dataset" into
tagged_object
at the bottom of the stack:Checklist