GitHub user tenthe added a comment to the discussion: Support IoTDB as Time Series Storage
There may be cases that don't work properly, but so far I haven't had any problems with it. In general, when writing data to the data lake, the user can decide whether the event schema should be overwritten or extended. <img width="752" alt="grafik" src="https://github.com/apache/streampipes/assets/5279561/fba27ec2-256a-4066-a463-aebae6b32cfb";> The old data should always remain in influx, and the new data is written according to the new schema. The difference with influx is that the measurement does not change. For the IoTDB, we would have to adjust the path of the measurement. How can we then access the data already stored? Do we need to migrate them or do we need to follow the legacy paths? For influx, I believe the data is still available. But it is also possible that I am wrong here, are there other experiences with this? GitHub link: https://github.com/apache/streampipes/discussions/2857#discussioncomment-9458622 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
