GitHub user A0R0P0I7T added a comment to the discussion: [GSoC 2026 Aspiring Contributor] Introducing Myself – Flink Connector for Apache IoTDB 2.X Table Mode
Hi everyone, Quick progress update since my introduction post. Over the past day I have been moving beyond documentation and into actual implementation. I have completed three core components of the FLIP-27 based connector — `IoTDBSplit` defining time-range boundaries (splitId, startTime, endTime) as the unit of parallelism, `IoTDBSplitSerializer` handling serialization for network transfer and checkpointing, and `IoTDBSplitEnumerator` managing split creation, assignment, and recovery. Key things I worked through: - How `addSplitsBack` recovers all splits from a failed reader and why it takes a List even when assigning one split at a time - Why split immutability matters for checkpoint consistency and where currentOffset actually belongs - How `SplitEnumeratorContext` acts as the communication bridge between the enumerator and Flink's JobManager - How `snapshotState` fits into Flink's barrier-based checkpointing mechanism The biggest challenge was understanding the exact boundary between what the enumerator manages and what Flink's framework handles automatically — particularly around reader failure and split reassignment, which required careful study before the design became clear. The next step is the `IoTDBSourceReader` — the most critical remaining component where actual IoTDB session interactions, RowData emission, and per-split progress tracking happen. I have back-to-back exams over the next two days so work on the `IoTDBSourceReader` will begin the day after tomorrow. Progress has been slow due to these MidSems but the POC will be completed by Sunday and pushed to the previously mentioned repo. Looking forward to any feedback from the community. Arpit Saha GitHub link: https://github.com/apache/iotdb/discussions/17248#discussioncomment-16014918 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
