venkatamandavilli-code commented on issue #39827: URL: https://github.com/apache/superset/issues/39827#issuecomment-4471355663
Interesting proposal. The browser dependency around `query_context` generation has been a limitation for API-driven and headless workflows for quite some time, especially for integrations that treat Superset primarily as a backend analytics service. Using a dedicated internal service to reuse the existing frontend `buildQueryContext` logic feels more maintainable than trying to duplicate plugin-specific behavior in Python. The lazy hydration approach also seems practical since it avoids unnecessary regeneration while still supporting API-created charts and background jobs. One thing that may be worth considering is version compatibility between the backend and the Node sidecar service, especially as chart plugins evolve independently over time. It may help to ensure plugin/runtime mismatches are surfaced clearly through logging or compatibility checks. The proposed `force=true` refresh behavior also seems useful for automated workflows and report generation scenarios where `form_data` changes programmatically. Overall, this feels like a reasonable direction for reducing frontend coupling in API-first Superset deployments. -- 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]
