PDGGK opened a new pull request, #137: URL: https://github.com/apache/iotdb-extras/pull/137
The latest-value route of `iotdb-thingsboard-table` needs `iotdb.ts_latest.cluster_mode` set to `sticky-routing` or `disabled`; `IoTDBTableLatestDao` checks it when it is constructed. The migration guide's selector table and its step 3 example leave the property out, so following the example as written stops ThingsBoard at startup with: ``` IllegalStateException: iotdb.ts_latest.cluster_mode must be explicitly set to 'sticky-routing' or 'disabled' when the IoTDB Table Mode latest overlay DAO is active; got ''. ``` I checked this on master (57aa0d9) with a Spring context built from the three properties in step 3. It fails with the exception above, and it starts, with the latest DAO present, once `iotdb.ts_latest.cluster_mode=sticky-routing` is added. This adds the property to the table and the example and says what the two values mean, as the guide already does for `iotdb.attributes.cluster_mode`. It also removes the note that the attributes route needs a ThingsBoard build exposing an attribute selector "no shipped release does yet". The module supplies that selector and withdraws `JpaAttributeDao` itself on ThingsBoard 4.3.1.2, as the README and the user guide say, so the note is out of date. Documentation only. -- 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]
