eaugene commented on issue #11024: URL: https://github.com/apache/pinot/issues/11024#issuecomment-1618142759
@kishoreg Thanks for the questions. 1. The initial version of WebSocket Endpoint won't be for the standing queries. Web Socket would serve as one additional interface ( than existing REST API way) for an external system to connect and query in Pinot, here we save the connection establishment time for each HTTP request . The client is expected to give any queries as we currently have with REST API. 2. The additional use cases of making it support standing queries to period response/return after a change in data ( with a periodic check at pinot ) can be added once the underlying web socket interface is there. This would be a nice feature to support at Pinot as it removes the work at the client system ( particularly data viz. applications ) to periodically call Pinot. 3. For incremental results bounded to standing queries, we can this support once point 2 is made. Here we can utilise the time field of real-time data flowing in & a WebSocket connection at the pinot broker end can maintain the state of the last timestamp it served. @atris Please add if I am missing any points. -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
