You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by 王旋 <cr...@gmail.com> on 2026/05/06 02:41:12 UTC
Welcome to GSoC 2026 – Enhancing ThingsBoard Integration with IoTDB 2.X Table Mode
Hi Zihan,
Congratulations and a warm welcome to the Apache IoTDB community! 🎉
Your GSoC 2026 proposal – *"Enhancing ThingsBoard Integration with IoTDB
2.X Table Mode"* – has been accepted. I am very pleased to be your mentor
for this project, and I look forward to working with you over the coming
months.
Your proposal stood out not only because of its technical depth (single
generic table design, Tablet-based writes, SQL aggregations, TTL retention)
but also because you have already delivered a working PoC, engaged with
both communities early (ThingsBoard Discussion #15296, IoTDB Discussion
#17352), and demonstrated a clear commitment to cross-community
collaboration. Your existing contributions to Apache IoTDB (#17212), Beam,
ShardingSphere, and Iceberg give me confidence that you will execute this
project successfully.
------------------------------
Community Bonding Period (May 1 – May 24)
Before coding starts on May 25, please focus on the following:
1.
Introduce yourself to the Apache IoTDB dev mailing list (if you haven’t
already) – share a brief background and a link to your proposal.
2.
Set up your development environment – ensure you can run ThingsBoard +
IoTDB 2.0.5 (or newer) with your PoC locally. Document any setup issues you
encounter – that will help future users.
3.
Refine the design document – I’d like you to post a detailed design doc
(based on your proposal) on the mailing list for community feedback before
coding begins. Include final decisions on the attribute table schema
(per-scope tables vs. scope-in-key encoding) and label handling.
4.
Confirm the weekly sync schedule – please reply with your availability
for a 30-minute video call every Monday (or Tuesday) . My timezone is
UTC+8; you are UTC+10. Let’s aim for a time that works consistently.
------------------------------
Communication and Collaboration
We will use the following channels:
Purpose Channel
Public technical discussions dev@iotdb.apache.org (please keep mail
threading clean)
Code reviews GitHub PRs (target apache/iotdb-extras first, then ThingsBoard)
Quick questions / daily chat WeChat
Weekly status Email to me (and optionally cc dev list for visibility)
Language: We can use Chinese for day-to-day discussions – that will make
communication faster and more precise. For public mailing list posts,
please use English so the whole community can follow.
Weekly status update: Every Friday (or Monday before our sync), please send
a brief email answering:
-
What did you complete this week?
-
What will you do next week?
-
Are there any blockers?
------------------------------
Project Milestones (based on your proposal)
We will follow the 12‑week plan you proposed, with these key deliverables:
Phase Weeks Focus Mid‑term check
1. Design & Prototype 1–3 Final schema, session management, write/read PoC
integrated into DAO –
2. Core DAO Implementation 4–7 TimeseriesDao, LatestDao, AttributeDao with
full type mapping + unit tests Mid‑term evaluation (end of Week 6)
3. Aggregation & Retention 8–10 Dashboard aggregations (date_bin, COALESCE),
TTL management, integration tests –
4. Polish & Migration 11–12 Performance benchmarks (comparison table vs
tree model), migration guide, blog post Final evaluation (end of Week 12)
Important evaluation deadlines (to be confirmed with org admin):
-
Mid‑term evaluation: early July (exact date TBC)
-
Final evaluation: late August
You must push code regularly and keep your GSoC timeline page updated. If
you hit any blocker, tell me within 24 hours – we will adjust the plan
together.
------------------------------
Time Commitment
GSoC expects approximately 35 hours per week during the coding period (May
25 – August 24). Please confirm that you can commit this amount of time. If
you have any other commitments (exams, part-time work) during that period,
let me know as early as possible so we can plan around them.
------------------------------
Code Repository and Workflow
-
Initial development will happen in a branch of your fork of
apache/iotdb-extras (since the integration is a connector, not core
IoTDB).
-
We will create a new module: iotdb-thingsboard-table.
-
Once stable, we will prepare a pull request to ThingsBoard adding
database.ts.type=iotdb-table as a new backend option.
-
Code must include unit tests (using embedded or Dockerized IoTDB) and
follow the existing ThingsBoard DAO patterns.
-
All PRs must pass CI (check ThingsBoard’s requirements).
I will review your code promptly (within 48 hours) and provide constructive
feedback. Please be prepared to respond to review comments quickly – that’s
how we maintain momentum.
------------------------------
Important Reminders
-
Public communication first – technical decisions should be made on the
mailing list (or at least summarized there). Private chat is for
coordination only.
-
Respect both communities – When posting to ThingsBoard channels, frame
the work as a contribution to ThingsBoard, not just “IoTDB’s new feature”.
We are building a bridge.
-
Mid‑term and final evaluations are mandatory – If you fail to submit
them on time, you automatically fail GSoC. I will remind you, but please
mark your calendar.
------------------------------
Immediate Action Items
Please reply to this email (and cc dev@iotdb.apache.org) with:
1.
Your preferred day/time for our weekly sync (UTC+10 for you, UTC+8 for
me).
2.
Confirmation that you can run the ThingsBoard + IoTDB 2.x environment
locally (or any issues you face).
3.
A brief introduction post to the mailing list (send it as a separate
email, but let me know when you do).
Once again, welcome aboard! I am excited to see this integration become a
reality. Let’s make this a great summer of code.
Best regards,
Xuan Wang
GSoC Mentor | Apache IoTDB
Re: Welcome to GSoC 2026 – Enhancing ThingsBoard Integration with IoTDB 2.X Table Mode
Posted by Zh D <dz...@gmail.com>.
Hi Xuan,
Thanks for the detailed onboarding plan. My responses are below.
1. Weekly sync schedule
My preferred slot is Monday 14:00 AEST / 12:00 CST. I can also do any
30-minute window on Monday 14:00-17:00 AEST / 12:00-15:00 CST if that suits
your calendar better. I can keep the selected slot fixed for the duration
of GSoC.
2. Local environment
Confirmed. The PoC from my proposal -- write path with Tablet-based inserts
and read path covering the dashboard aggregation queries -- runs locally
against ThingsBoard with IoTDB 2.0.5. I'll re-validate against the current
2.0.8 release this week and keep a setup-issues log during the bonding
period; that should later feed into the migration guide and blog post.
3. Self-introduction post
I'll send a separate introduction to dev@iotdb.apache.org today, with a
brief background and links to the GSOC-304 proposal/design discussion (
https://github.com/apache/iotdb/discussions/17352) and the cross-community
thread on the ThingsBoard side (
https://github.com/thingsboard/thingsboard/discussions/15296).
Time commitment
Confirmed: ~35 hours/week from May 25 through August 24.
Two further points:
- I'll post the refined design document to dev@iotdb.apache.org by Sunday,
2026-05-17, with a concrete recommendation and trade-offs on the two open
questions from #17352 (attribute table schema: per-scope tables vs.
scope-in-key encoding, and label handling), then ask the list for feedback.
- Acknowledged on public-first technical decisions, summarising
private-chat outcomes back to the list, weekly status updates (Friday, or
the Monday before our sync), GSoC timeline-page updates, and reporting
blockers within 24 hours. Mid-term evaluation (2026-07-10 18:00 UTC /
2026-07-11 04:00 AEST) and the final evaluation window are on my calendar.
Best regards,
Zihan Dai
GitHub: https://github.com/PDGGK
University of Melbourne
On Wed, May 06, 2026 12:41 PM, 王旋 <cr...@gmail.com> wrote:
> Hi Zihan,
>
> Congratulations and a warm welcome to the Apache IoTDB community! 🎉
>
> Your GSoC 2026 proposal – *"Enhancing ThingsBoard Integration with IoTDB
> 2.X Table Mode"* – has been accepted. I am very pleased to be your mentor
> for this project, and I look forward to working with you over the coming
> months.
>
> Your proposal stood out not only because of its technical depth (single
> generic table design, Tablet-based writes, SQL aggregations, TTL retention)
> but also because you have already delivered a working PoC, engaged with
> both communities early (ThingsBoard Discussion #15296, IoTDB Discussion
> #17352), and demonstrated a clear commitment to cross-community
> collaboration. Your existing contributions to Apache IoTDB (#17212), Beam,
> ShardingSphere, and Iceberg give me confidence that you will execute this
> project successfully.
> ------------------------------
> Community Bonding Period (May 1 – May 24)
>
> Before coding starts on May 25, please focus on the following:
>
> 1.
>
> Introduce yourself to the Apache IoTDB dev mailing list (if you
> haven’t already) – share a brief background and a link to your proposal.
> 2.
>
> Set up your development environment – ensure you can run ThingsBoard +
> IoTDB 2.0.5 (or newer) with your PoC locally. Document any setup issues you
> encounter – that will help future users.
> 3.
>
> Refine the design document – I’d like you to post a detailed design
> doc (based on your proposal) on the mailing list for community feedback
> before coding begins. Include final decisions on the attribute table schema
> (per-scope tables vs. scope-in-key encoding) and label handling.
> 4.
>
> Confirm the weekly sync schedule – please reply with your availability
> for a 30-minute video call every Monday (or Tuesday) . My timezone is
> UTC+8; you are UTC+10. Let’s aim for a time that works consistently.
>
> ------------------------------
> Communication and Collaboration
>
> We will use the following channels:
> Purpose Channel
> Public technical discussions dev@iotdb.apache.org (please keep mail
> threading clean)
> Code reviews GitHub PRs (target apache/iotdb-extras first, then
> ThingsBoard)
> Quick questions / daily chat WeChat
> Weekly status Email to me (and optionally cc dev list for visibility)
>
> Language: We can use Chinese for day-to-day discussions – that will make
> communication faster and more precise. For public mailing list posts,
> please use English so the whole community can follow.
>
> Weekly status update: Every Friday (or Monday before our sync), please
> send a brief email answering:
>
> -
>
> What did you complete this week?
> -
>
> What will you do next week?
> -
>
> Are there any blockers?
>
> ------------------------------
> Project Milestones (based on your proposal)
>
> We will follow the 12‑week plan you proposed, with these key deliverables:
> Phase Weeks Focus Mid‑term check
> 1. Design & Prototype 1–3 Final schema, session management, write/read
> PoC integrated into DAO –
> 2. Core DAO Implementation 4–7 TimeseriesDao, LatestDao, AttributeDao with
> full type mapping + unit tests Mid‑term evaluation (end of Week 6)
> 3. Aggregation & Retention 8–10 Dashboard aggregations (date_bin, COALESCE),
> TTL management, integration tests –
> 4. Polish & Migration 11–12 Performance benchmarks (comparison table vs
> tree model), migration guide, blog post Final evaluation (end of Week 12)
>
> Important evaluation deadlines (to be confirmed with org admin):
>
> -
>
> Mid‑term evaluation: early July (exact date TBC)
> -
>
> Final evaluation: late August
>
> You must push code regularly and keep your GSoC timeline page updated. If
> you hit any blocker, tell me within 24 hours – we will adjust the plan
> together.
> ------------------------------
> Time Commitment
>
> GSoC expects approximately 35 hours per week during the coding period
> (May 25 – August 24). Please confirm that you can commit this amount of
> time. If you have any other commitments (exams, part-time work) during that
> period, let me know as early as possible so we can plan around them.
> ------------------------------
> Code Repository and Workflow
>
> -
>
> Initial development will happen in a branch of your fork of
> apache/iotdb-extras (since the integration is a connector, not core
> IoTDB).
> -
>
> We will create a new module: iotdb-thingsboard-table.
> -
>
> Once stable, we will prepare a pull request to ThingsBoard adding
> database.ts.type=iotdb-table as a new backend option.
> -
>
> Code must include unit tests (using embedded or Dockerized IoTDB) and
> follow the existing ThingsBoard DAO patterns.
> -
>
> All PRs must pass CI (check ThingsBoard’s requirements).
>
> I will review your code promptly (within 48 hours) and provide
> constructive feedback. Please be prepared to respond to review comments
> quickly – that’s how we maintain momentum.
> ------------------------------
> Important Reminders
>
> -
>
> Public communication first – technical decisions should be made on the
> mailing list (or at least summarized there). Private chat is for
> coordination only.
> -
>
> Respect both communities – When posting to ThingsBoard channels, frame
> the work as a contribution to ThingsBoard, not just “IoTDB’s new feature”.
> We are building a bridge.
> -
>
> Mid‑term and final evaluations are mandatory – If you fail to submit
> them on time, you automatically fail GSoC. I will remind you, but please
> mark your calendar.
>
> ------------------------------
> Immediate Action Items
>
> Please reply to this email (and cc dev@iotdb.apache.org) with:
>
> 1.
>
> Your preferred day/time for our weekly sync (UTC+10 for you, UTC+8 for
> me).
> 2.
>
> Confirmation that you can run the ThingsBoard + IoTDB 2.x environment
> locally (or any issues you face).
> 3.
>
> A brief introduction post to the mailing list (send it as a separate
> email, but let me know when you do).
>
> Once again, welcome aboard! I am excited to see this integration become a
> reality. Let’s make this a great summer of code.
>
> Best regards,
>
> Xuan Wang
> GSoC Mentor | Apache IoTDB
>