Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion - Add Pagination to Table Queries #528

Open
joewood opened this issue Dec 13, 2017 · 1 comment
Open

Suggestion - Add Pagination to Table Queries #528

joewood opened this issue Dec 13, 2017 · 1 comment
Labels
enhancement P1 Slightly lower priority to P0 ;) query-engine Issues owned by the ksqlDB Query Engine team

Comments

@joewood
Copy link

joewood commented Dec 13, 2017

The KSQL interface over REST currently returns an HTTP stream of data for a query on a table. This makes it difficult to serve multiple consumers (e.g. same table, multiple dashboards) and page through large KTables. This makes browsing data difficult for large amounts of data. A couple of suggestions:

  • Add the ability to query a page of data using the LIMIT keyword, but also adding an OFFSET as the starting marker (e.g. the KTable key)
  • Add the ability to consume KTable (and stream) updates over HTTP using a unique consumer id (similar to the Kafka REST Proxy).
@Taymindis
Copy link

Taymindis commented Nov 6, 2023

while waiting for this solution, just use Apache FlinkSQL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement P1 Slightly lower priority to P0 ;) query-engine Issues owned by the ksqlDB Query Engine team
Projects
None yet
Development

No branches or pull requests

4 participants