shauryachats opened a new issue, #16287: URL: https://github.com/apache/pinot/issues/16287
After the timeseries engine was introduced in Pinot 1.3 as an experimental feature, it is currently being worked upon to make it generally available (GA) in subsequent Pinot releases. An important part of making it GA is to have a dedicated controller UI query environment for timeseries queries to make it more intuitive for users to write, test, and visualize their queries without relying on making HTTP calls to the relevant endpoints. As a part of that, I would like to propose an initial mock-up for the timeseries query UI. <img width="1787" height="1004" alt="Image" src="https://github.com/user-attachments/assets/d7db9203-17df-4728-af9d-3318635b6df6"; /> The timeseries query flow lives within the query console alongside the regular query flow. It borrows the theme and design from the query flow, and as an MVP, would support formatted JSON as the output. The initial timeseries query UI has: - Ability to select query language (currently only M3QL is supported). - Similar to regular query UI, the query params will be included in the URL to be copied and executed seamlessly. - The output is formatted JSON and can be conveniently copied. The initial timeseries query UI would be enough for the basic queryability. Future items are planned to improve this UI further. - [P1] Integrate Grafana plugins for more intuitive visualization of the timeseries data. - [P2] Generate sample queries for a table based on the query language (non-trivial because each table can have a different time column, and the syntax for each language is different). - [P3] Syntax-aware editor and format query for the time series queries. Please feel free to suggest any improvements in the initial mock-up, and also suggest any more future action items for this flow. Thanks! -- 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]
