PDGGK commented on issue #18258: URL: https://github.com/apache/iotdb/issues/18258#issuecomment-5180694245
Status update, since this has been assigned to me and the thread has not been told what landed. **On the native-client suggestion.** Adopted, and it is in the merged code — thanks @HTHou for raising it originally. The table-model path in iotdb-extras#114 goes through `apache/iotdb-client-go` v2 (v2.0.8) over the native protocol rather than REST. That PR merged on 2026-07-23. **What is delivered.** Table-model *querying*: a mode selector, raw SQL with a database field, native-client execution, and both time-series and table result formats, with the row/column contract pinned by tests against a real server. **What is not.** Three things, and I would rather be explicit than let this look further along than it is: 1. **The database → table → column browser** is not built. Table mode currently takes SQL, not a guided selection, so the discoverability half of Problem 1 is still open. 2. **The tree-model UX section (2.1–2.6) is untouched.** The stale aggregate list this issue quotes is still exactly that array on master. 3. **Modernization is partial.** iotdb-extras#118 moves the frontend off the archived `@grafana/toolkit` to `@grafana/create-plugin`, which is one of the three bullets under item 3 and only its frontend half. That PR is open and currently has review comments to address. So of the three top-level asks here, roughly half of one is done. I do not think this should be closed. **Proposed order** -- this is my plan unless the maintainers would rather reprioritise: finish #118, then the DB→table→column browser (it is the piece that makes table mode usable without knowing the schema), then the tree-model UX items, which are the largest and least entangled with the rest. I also owe this thread a screenshot of the plugin running against a real Grafana rather than only test output; I will attach that on #118. -- 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]
