ablanchard commented on issue #28446:
URL: https://github.com/apache/superset/issues/28446#issuecomment-2167569789
From my understanding of the problem:
- When you export charts, query_context is present in the exported files
but the id for the datasource and the slice are not converted to uuid so the
query_context is useless when you import it to a different instance.
- To avoid [a bug when you import, a process has been
added](https://github.com/apache/superset/pull/23582) to remove the
query_context entirely, [still present in
master](https://github.com/preset-io/superset/blob/daf37cbe585515afe725d266ee6ac292b2a00c44/superset/commands/importers/v1/assets.py#L118)
- Then the new security layer fails because the query context is empty
So a fix could be around properly export the charts in the first place and
stop removing the query_context when importing.
A temporary workaround is to update the charts using the api, based on the
exported query_context. Of course if you are exporting and importing on a
different instance, you need to change ids references in the query_context
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org
