rusackas commented on issue #9190:
URL: https://github.com/apache/superset/issues/9190#issuecomment-2206670957
Agreed with Michael on all points. And I'm very thankful for all of your
insights and input here. I'd be SO excited to see this feature mainstream, and
I think both the UX will improve as well as the infra scenario.
Is there any down side to just making Redis a required component, if that
simplifies things further?
Also, just to play devil's advocate on the removal of websockets, there were
two distinct advantages I kind of dream of:
1) We wouldn't have to have any sort of polling backoff OR hammer a polling
API. Results would always come in sooner rather than later, improving the UX.
2) Having a websocket that's made aware of chart data endpoints opens
numerous other doors... whether it's the redis result cache being
invalidated/updated ("there's fresh data for your query, come get it!"), or
even the possibility of getting _much_ more frequent data, i.e. realtime events
streaming from Kafka/Influx/etc.
3) Having a websocket connection also provides a door to solve a variety of
other UX problems we have, e.g. token expiration awareness, or potentially
notifications about _anything_ (reports being sent, chat messages, schema
updates, dashboards being updated while you're looking at them, etc).
At some point, I think we'll want any or all of the above, so we'll want to
revisit the idea of having a websocket solution in place. If this is not the
time, so be it... mainstreaming GAQ would be a clear priority. But if there's
anything worth keeping/shelving here for a future effort, it seems
_potentially_ worth it.
--
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]
