Hi Anukalp,

Thank you for your strong interest in the Apache IoTDB Flink connector
project. We are impressed with your thorough preparation and understanding
of the project's goals.

Regarding your questions, here is some guidance:

   - *Research Focus:* We recommend you start by delving into the Source
   and Sink implementations for the *Tree Mode* within the existing
   flink-iotdb-connector[1]. This will provide you with a solid
   understanding of the current data flow and architecture, which is key to
   identifying the refactoring or challenges required to properly
adapt it for *Table
   Mode*. Your plan to explore Table Mode SQL features is also excellent.
   - *API Prioritization:* Given that the Flink Table API is the primary
   integration path for many users, I suggest focusing your initial proposal
   and implementation on strong *Table API* support to quickly achieve a
   Minimal Viable Product (MVP) for core read/write functionality. However,
   the *DataStream API* is the underlying foundation, and a complete
   connector should ideally support both, so please keep it in mind for the
   overall design.

Your initial steps are sound. We encourage you to share your exploratory
findings or any preliminary design ideas with us, perhaps as a Pull Request
(PR) or another Discussion thread, so we can provide more specific feedback.

Looking forward to your proposal!

[1]
https://github.com/apache/iotdb-extras/tree/master/connectors/flink-iotdb-connector


Best regards,
---------------------
Yuan Tian


On Sat, Jan 31, 2026 at 7:54 PM anukalp2804 (via GitHub) <[email protected]>
wrote:

>
> GitHub user anukalp2804 created a discussion: [GSoC 2026] Flink connector
> for IoTDB table mode – prospective contributor
>
> Hello,
>
> I’m Anukalp, a CS undergraduate with a strong interest in Java-based
> backend and data integration systems. I’ve been going through the GSoC idea
> around building a Flink connector for Apache IoTDB 2.X table mode, and the
> scope and motivation behind the project are very clear and interesting.
>
> From my understanding, the existing Flink connectors mainly focus on the
> tree mode, and this project aims to provide first-class support for IoTDB’s
> table mode through Flink’s DataStream and Table APIs, including schema
> mapping, read/write support, and fault tolerance.
>
> I’m preparing for GSoC 2026 and plan to start by exploring the existing
> `flink-iotdb-connector`, the table-mode SQL features in IoTDB 2.X, and
> Flink’s connector architecture. I had a couple of questions:
>
> - Are there specific modules or existing connectors you would recommend
> focusing on first to better understand the current limitations around table
> mode?
> - For the initial implementation, do you see it leaning more toward the
> Flink Table API, or should both the Table and DataStream APIs be considered
> from the beginning?
>
> I’d appreciate any guidance on how to prepare effectively and where early
> exploratory contributions would be most useful.
>
> Thank you for your time.
>
> GitHub link: https://github.com/apache/iotdb/discussions/17128
>
> ----
> This is an automatically sent email for [email protected].
> To unsubscribe, please send an email to: [email protected]
>
>

Reply via email to