PiXOT97 commented on issue #33561: URL: https://github.com/apache/superset/issues/33561#issuecomment-2904661118
@rusackas - done some tests today on this issue, here is what i have found: TEST 1 - Embedded Dashboard (launch website) ``` - Went into REDIS and flushed both DB. (kept only the binding.celery) - Launched the Embedded Website - Result Redis: Generated 2 keys but there is no ""async-events" generated - Result WebApp: Unexpected Error ```  TEST 2 - Embedded Dashboard (refresh dashboard) ``` - Kept the same session opened. - Went into REDIS and flushed both DB. (kept only the binding.celery) - Pressed "Refresh Dashboard" - Result Redis: Generated 1 key but there is no "async-events" generated - Result WebApp: Chart has loaded the data ```  TEST 3 - Directly loaded the dashboard from the Superset ``` - Login into Superset + Navigated to the dashboard - Went into REDIS and flushed both DB. (kept only the binding.celery) - Reloaded the page - Result Redis: Generated all the keys and also all the "async-events - Result WebApp: Chart has loaded the data ```  It appears that the superset-embedding SDK is not utilizing the asynchronous query infrastructure (GLOBAL_ASYNC_QUERIES and async-events) when rendering the embedded dashboard, not even when hitting "Refresh Dashboard" because in every embedded scenario, Redis doesn't generate any async-events, which means Superset isn’t treating these as async queries. On the other hand, when loading the same dashboard directly through the Superset UI, everything works fine, async-events are triggered, Redis keys are created, and the chart is loading as expected. So it looks like the embedding flow is bypassing async completely. Let me know your thoughts on this. -- 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]
