feat: provide basic support for IoTDB as time series storage #2835
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
dependencies
tenthe
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This PR introduces very basic and experimental support for IoTDB as time series store for StreamPipes. By default, InfluxDB is still the time series storage of choice but by setting the following environment variables IoTDB can be used as storage.
SP_TS_STORAGE:iotdbSP_TS_STORAGE_HOST:<THE-HOST-OF-YOUR-IOTDB-INSTANCE>SP_TS_STORAGE_PORT:<THE-PORT-OF-YOUR-IOTDB-INSTANCE>These need to be set in the core and the extensions services.
Important
As of now this only supports persisting data into IoTDB via the Data Lake sink. Several other functionalities are not yet implemented and cause breakages, e.g., in the Data Explorer. These functionalities will be provided with upcoming PRs.
Remarks
PR introduces (a) breaking change(s): no
PR introduces (a) deprecation(s): no