Hi Alessandro, Thank you for your interest in the Trino-IoTDB Connector project for GSoC 2026. Your background as a Big Data Engineer and your experience with Spark and distributed systems will be very valuable for this project.
To answer your questions: 1. Scope and Priority: For the GSoC period, our primary priority is a robust, fully functional read-only connector. This includes efficient schema mapping, predicate and agg pushdown. Write support can be considered a secondary goal if time permits, but a high-quality read implementation is the priority. 2. Starting Point: You can try to implement `from-first-syntax`[1] in IoTDB which can help you understand the parser phase and then you can implement `group-by-all`[2] syntax in iotdb which can help you understand the analyzer phase. 3. Prior Work: There is currently no active prototype for a Trino-specific connector in the main repository, but I think you can refer to iotdb-spark-connector[3] Please let me know if you have any other questions as you begin drafting your formal proposal. [1] https://duckdb.org/docs/stable/sql/query_syntax/from#from-first-syntax [2] https://duckdb.org/docs/stable/sql/query_syntax/groupby#group-by-all [3] https://github.com/apache/iotdb-extras/pull/51 Best regards, Yuan Tian On Fri, Mar 20, 2026 at 12:58 AM Alessandro Cingolani < [email protected]> wrote: > Hi Yuan, > > My name is Alessandro, and I am writing to express my interest in the > Trino-IoTDB Connector project proposed for GSoC 2026 (GSOC-303). > > I am a Big Data Engineer currently working with Spark, Airflow, Hadoop, and > Python on a daily basis. While I am relatively new to open source > contribution, I have hands-on experience with distributed data processing > and pipeline design in production environments — which I believe gives me a > grounded perspective on the practical value of enabling OLAP queries over > time-series data via Trino. > > I am familiar with query engine concepts through my work with Spark, and I > have been reviewing the Trino connector developer guide as well as a > starting reference. I find the core challenges of this project — schema > mapping, predicate pushdown — genuinely interesting from a real-world data > architecture standpoint. > > Before I proceed with drafting a formal proposal, I would appreciate your > guidance on a few points: > > 1. Is there a preferred scope or deliverable you would prioritize for the > GSoC period — for example, a fully functional read-only connector versus a > more complete implementation including write support? > > 2. Are there existing issues or discussion threads in the IoTDB repository > that you would recommend as a starting point to understand the codebase > before the proposal submission? > > 3. Is there any prior work or prototype related to this connector that I > should be aware of, to avoid duplicating efforts? > > Thank you for your time and for making this project available through GSoC. > I look forward to hearing from you and to potentially contributing to the > IoTDB ecosystem. > > Best regards, > Alessandro >
