[PDGGK]

What

Adds a user-guide page for the iotdb-thingsboard-table module in apache/iotdb-extras, which lets a stock ThingsBoard instance store telemetry and attributes in IoTDB 2.x table model by putting the module and its runtime dependencies on its classpath and setting a few properties. (The page lists the exact jar set; it is not a single jar.)

The page is modelled on the existing Spark-IoTDB page — overview first, then requirements and deployment — and adds Configuration and Known Limitations sections that this integration needs.

Why a second ThingsBoard page

The site already has a ThingsBoard page under the tree model, but it documents a different deployment — an IoTDB-adapted ThingsBoard package writing to root.thingsboard. This one is stock ThingsBoard plus the module and its runtime dependencies, against table model.

Rather than replace or merge them, the new page opens with a paragraph distinguishing the two and links across to the tree-model page, so a reader who has landed on the wrong one can get to the right one.

That link is currently one-directional — the tree-model page does not point back here. Making it symmetric is a follow-up I have deliberately left out of this PR; see the last note below.

Files (10)

new	Thingsboard.md in latest-Table and Master/Table, EN + ZH
modified	en-Table.ts / zh-Table.ts sidebars — new "IoT Platform" / "物联网对接" group
modified	Ecosystem-Overview_apache.md index row in all four trees

Notes for reviewers

• No screenshots. In this directory the screenshot-heavy pages are the GUI clients — DBeaver has 11, DataGrip 13. The code-integration pages carry few or none: SeaTunnel, Mybatis-Generator and Spring-Boot-Starter have zero, MyBatisPlus-Generator has one, Spark-IoTDB two. This page is a code integration, so I left them out rather than manufacture images. I have since run the deployment end to end (ThingsBoard 4.3.1.2 against IoTDB 2.0.8), so real screenshots are now possible — say the word and I will add them.
• Cross-tree links differ by tree because the layout requires it: from latest-Table the tree-model page is at ../../latest/, from Master/Table it is at ../../Tree/. There is no Master/latest and no top-level Tree, so exactly one of these resolves per copy.
• The back-link is not in this PR. The tree-model ThingsBoard page exists in four version trees (V1.3.x, dev-1.3, latest, Master/Tree) in both languages, so a blanket back-link is 8 files. I would suggest scoping it to latest and Master/Tree (4 files) rather than all eight: V1.3.x and dev-1.3 document IoTDB versions that have no table model, so pointing them at a table-model integration would advertise something those versions cannot run. Happy to do that as a follow-up, or fold it in here if you would rather it land together.

The module is the deliverable of GSoC 2026 project GSOC-304, mentored by @CritasWang, who asked for this page.

[CritasWang]

@PDGGK add some's screenshots

[PDGGK]

@CritasWang The screenshots you asked for are in section 4 (the device's latest telemetry and client attributes pages), added in 3bac99e. I have also updated the page for the 2.0.11 release: it now downloads iotdb-thingsboard-table-2.0.11.jar from the release and the nine IoTDB client jars from Maven Central, instead of building from a commit. I followed the updated steps on ThingsBoard 4.3.1.2 with IoTDB 2.0.11: the commands give the ten jars with a good signature, ThingsBoard starts, and telemetry and a client attribute sent through ThingsBoard read back from IoTDB with the same timestamps.