PDGGK commented on issue #18258: URL: https://github.com/apache/iotdb/issues/18258#issuecomment-5021897327
I'd like to take this on. It spans the frontend, the Go backend, and the REST layer, so I'd approach it incrementally: 1. **Table model support first** — a tree/table switch in QueryEditor, a database → table → column browser, and standard SQL against table-model data, reusing IoTDB's existing SQL query interface where possible rather than adding new REST endpoints. 2. **Tree-model UX** next — a visual Query Builder with the raw SQL editor kept as the advanced mode, path-picker performance (caching / batch loading / search), and syncing the aggregate function list. 3. **Modernization alongside** — Grafana plugin SDK upgrade and the Go backend cleanup (`ioutil`, error handling, the `values` contract). I'd start with a focused, independently-reviewable PR for table-model querying, then iterate. Happy to adjust the sequencing if you'd prefer a different starting point. -- 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]
