vrajat opened a new issue, #13185: URL: https://github.com/apache/pinot/issues/13185
Cursor support will allow Pinot clients to consume query results in smaller chunks. This feature allows * Clients to work with lesser resources esp. memory. * Application logic is simpler with cursors. For example an app UI paginates through results in a table or a graph. [Design Doc](https://docs.google.com/document/d/1po2unpTltir1ptpGkBV49U4iH5eGulOdqzAL_I4Ev5E/edit?usp=sharing) Cursor support can be implemented using [APIs similar to Trino](https://trino.io/docs/current/develop/client-protocol.html) or using [SQL Cursors similar to Postgres](https://www.postgresql.org/docs/16/sql-fetch.html). In V1, cursors will be implemented using APIs. The primary reason to choose APIs instead of a SQL interface is speed of execution. SQL cursors will be considered in the future. The expectation is that the implementation should be the same for APIs and SQL. Note that https://github.com/apache/pinot/issues/5246 also proposes query result pagination in Apache Pinot. This feature is inspired by the proposal. The major difference is using API cursors (and later Postgres SQL syntax) to iterate through the result set. -- 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.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
