Consider IoTDB version update (1.3.x vs 2.0.x)

[slawr]

Currently we are on IoTDB v1.3.3. There are useful feature improvements in later versions and we should consider upgrading.

Currently this means considering v1.3.x vs 2.0.x. 2.0.x adds a major new table data model to the existing tree data model

Summary task list:

• Update base CDSP docker service for IoTDB to new version
• Determine whether there are any breaking API changes since last version
• Update IoTDB access code if needed in IL, VISSR and RemotiveLabs components
• Sanity test IL access to IoTDB
• Sanity test VISSR access to IoTDB
• Sanity test RemotiveLabs access to IoTDB
• Announce changes to community once merged

[slawr]

v1.3.6 (current latest) 'all-bin.zip' download is 106MBytes.
v2.0.5 (current latest) 'all-bin.zip' download is 111MBytes.

Whilst runtime footprint is relevant for production for our R&D focus the table data model introduced in v2.0.x is an interesting feature. The table model more closely follows the relational DB model and has advantages such as easier compatibility with tools, including LLMs, that assume that model. Table model may also be advantageous when modelling domains defined in VDM.

The IoTDB maintainers have stated that performance of the table model is broadly similar to the tree model. v2.0.x still supports the tree model, i.e. you can use either.

It seems reasonable to make the decision to move to v2.0.x (2.0.5 at the time of writing) to enable access to the new IoTDB Table data model.

[slawr]

Docker update

No major changes found between 1.3.3 and 2.0.5 in either the online doc or reference docker compose in the source, except support for some new env variables to allow JVM memory config introduced in this commit. Unfortunately it sets default values at 1G and as we do not know the environment in which we run for now will leave this out.

[slawr]

IoTDB version 2.0.5 -> 2.0.6

Whilst this work was ongoing the upstream project released v2.0.6. After waiting for the official docker images to be created I migrated to 2.0.6

API updates

Found no breaking API changes that required updates to VISSR/RL/IL connectors.

Sanity test: VISSR

• VISSR connected to updated IoTDB container.
• Using VISSR web client confirmed that could get/set data in DB.

Sanity test: IL

• IL connected to updated IoTDB container.

[slawr]

Found some links in the CDSP IoTDB downsample example README to the upstream IoTDB doc that needed updating.

[slawr]

Placing on hold whilst wait for code review by @chrizmc