-
Notifications
You must be signed in to change notification settings - Fork 141
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
New response format to support visualization #168
Comments
Actually the format protocol is independent with the search/evaluation result, so the dimensions and axises should not be defined within the format. Instead, I suggest the frontend to gather necessary aggregation information when doing the drag&drop, for example to get the field to be aggregated on, and the name of the aggregated result etc. The output protocol provides the data columns in the format that frontend can use directly, and the metat data of column names and types.
|
revised:
|
Closing and feel free to reopen if anything else needed. Thanks! |
Is your feature request related to a problem? Please describe.
The observability visualization uses the SQL plugin as the query engine and consumes the PPL component of this plugin as the search language. The existing protocols are mostly to provide good service for the JDBC/ODBC connectors, but the frontend still needs to do much preprocessing before rendering the visualizations.
Describe the solution you'd like
The detailed proposal is noted in the comments of issue #162
Describe alternatives you've considered
Pending discussion for alternatives.
Additional context
See #162 for details.
The text was updated successfully, but these errors were encountered: