mistercrunch commented on issue #33615: URL: https://github.com/apache/superset/issues/33615#issuecomment-2923155524
[workaround] I think re-saving the chart would fix it (?) There's a wider refactor people have been talking about to fix this. The TLDR on the issue is that the mapping between the chart definition to the query object can only be done on the frontend (each plugin has it's own js logic to do this), and that in some cases the backend needs to run the query behind a given chart, like in this instance here, but more broadly in alerts & reports. I think there's a new migration in master that may help, though unclear if it'll generate a query_context if it doesn't exist. I think the plan is to run js in a subprocess on the backend (?) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
