DEV Community

Apache SeaTunnel
Apache SeaTunnel

Posted on

What It Takes to Become an Apache SeaTunnel Committer: Doyeon Kim's Story

#apacheseatunnel #opensource #datascience #ai

Do you remember the young contributor from South Korea whom we featured last year?

In our previous interview, From Newcomer to Power Contributor: South Korea’s Doyeon Kim Shines in Apache SeaTunnel in Just Six Months, we shared the story of a passionate newcomer who had already become one of the most active contributors in the Apache SeaTunnel community within just a few months of joining.

Fast forward two years, and we're excited to share some wonderful news: Doyeon Kim has officially been invited to become an Apache SeaTunnel Committer! 🎉👏

What's even more inspiring is that Doyeon is still a university student.

Through her exceptional curiosity, relentless commitment to learning, and consistently high-quality contributions to both the project and the community, she has earned the recognition and trust of contributors worldwide. Her growth over the past two years has been remarkable, and her promotion to Committer reflects the impact she has had on the Apache SeaTunnel ecosystem.

To celebrate this milestone, we sat down with Doyeon for another in-depth conversation.

How has her perspective evolved since our first interview? What challenges did she overcome along the way? And what lessons has she learned on her journey from student contributor to Apache SeaTunnel Committer?

Join us as we look back on her inspiring open-source journey and discover the experiences that helped shape the next chapter of her growth.

Personal Introduction

My name is Doyeon Kim, and my GitHub ID is dybyte.

I am currently a university student. My main technical interests are backend development, data integration, distributed systems, and Apache SeaTunnel.

I am especially interested in how data integration systems work internally, including connectors, checkpointing, failure recovery, and engine state
management.

Outside of development, I enjoy playing games, especially Overwatch.

Full Interview Transcript

  1. How long have you been involved in open source? What attracts you to open source?

I have been involved in open source for about one year.

What attracted me to open source was the opportunity to work together with many people on the same project. I found it very interesting and enjoyable that contributors from different backgrounds can discuss ideas, review code, and improve the project together.

I also like that open source communities are active and open. Through open source, I can learn not only from the code itself, but also from discussions, reviews, and the way experienced contributors think about problems.

  1. When did you start contributing to the Apache SeaTunnel community, and what motivated you to get involved?

I started contributing to Apache SeaTunnel in May 2025.

At first, I was mainly studying backend development and wanted to gain experience
by contributing to a real open source project. When I found SeaTunnel, I felt that the community was active, welcoming, and open to new contributors, so I decided to start contributing.

As I continued participating, I encountered many interesting problems related to connectors, engine behavior, checkpointing, and reliability. Through these experiences, my technical interests gradually expanded from backend development to data integration systems and distributed systems.

  1. Now that you have been elected as a SeaTunnel Committer, could you summarize your contributions to the community, including both code and non-code contributions? Please describe specific solutions or initiatives as much as possible.

My contributions to Apache SeaTunnel include code contributions, larger ongoing proposals, pull request reviews, technical discussions, documentation improvements, and community activities.

On the code side, I have mainly contributed to the Zeta engine, connectors, Transform-V2, tests, and documentation.

In the Zeta engine area, I worked on improving job state handling, metrics handling, REST API stability, and failure-related edge cases. For example:

These changes helped me better understand SeaTunnel’s engine behavior,
job lifecycle, metrics handling, and failure recovery paths.

I have also contributed to connector and Transform-V2-related improvements. For example:

These contributions involved fixing the connector or transform behavior, improving correctness, and adding new transform capabilities.

In addition to merged contributions, I have also been working on larger ongoing proposals and feature work. These PRs are still open, but I have already addressed the main review feedback, and they are currently waiting for further review or merge. I do not consider them completed features yet, but they represent areas where I have been investing deeper effort.

This PR introduces a BigQuery Sink connector based on the BigQuery Storage Write API. Through this work, I learned a lot about connector design, checkpoint integration, write semantics, and failure recovery.

This PR explores compaction support for IMap external storage. It helped me think more deeply about storage design, recovery behavior, and how to reduce long-term maintenance costs.

This PR proposes a StateStore abstraction layer in the Zeta engine. The goal is to reduce direct dependency on Hazelcast IMap and make engine state management easier to maintain and evolve. It represents one of the deeper areas I have been working on recently.

This PR is related to improving job state reporting and observability in the Zeta engine.

I have also helped improve test stability and CI reliability through several smaller fixes. Although these changes are not the main focus of my contributions, I believe they are still important for maintaining contributor productivity and community trust.

On the non-code side, I have reviewed pull requests from other contributors and participated in technical discussions. My reviews have covered areas such as connectors, Zeta engine behavior, configuration validation, tests, documentation, and maintainability.

During reviews, I try to focus not only on whether the code works, but also on whether the change is safe, understandable, and maintainable for the project in the long term.

I have also shared my experience through technical writing and SeaTunnel meetup participation. I hope these activities can help more people understand SeaTunnel and become interested in contributing to the community.

  1. After being involved in the SeaTunnel project and community for quite some time, you likely have a deep understanding of both. In your opinion, what differentiates SeaTunnel from other competing products/projects? What are its strengths and weaknesses? What aspects of the SeaTunnel community motivate you to stay actively involved?

In my opinion, SeaTunnel is especially useful when users need distributed data integration and need to connect many different sources and sinks.

One of SeaTunnel’s strengths is that it provides many connectors while also supporting distributed execution. This makes it useful for ETL and ELT scenarios where users need to move, synchronize, or transform data across different systems.

Another interesting point is that SeaTunnel has its own engine, Zeta, while
also supporting engines such as Flink and Spark. This gives users more flexibility depending on their use case.

At the same time, I think SeaTunnel is more focused on data integration than on being a full-featured stream processing engine. For very complex stream processing logic, such as advanced aggregations, windows, or event-time processing, engines like Flink or Spark may still be more suitable depending on the scenario.

The value of SeaTunnel may be especially clear in scenarios where users need to integrate many systems or process data at a larger scale, so it is important to evaluate it based on each company’s requirements.

What motivates me to stay involved is that SeaTunnel still has many meaningful problems to solve. The project is active, the community is open, and I feel that individual contributors can still have a real impact on the project.

  1. Have you ever performed re-development or custom enhancements to address SeaTunnel’s shortcomings? If so, have these improvements been contributed back to the community? Could you introduce the solution/design approach?

Since I am currently a student and not working in a company, I do not have experience customizing SeaTunnel for a company’s internal production use case.

However, through community contributions, I have worked on improvements that address limitations or potential reliability issues in SeaTunnel.

  1. Has your company used SeaTunnel? If yes, what are the use cases or scenarios? If not, would you consider recommending it to your company? What would be your reasons for recommending it?

Since I am currently a university student, I do not have a company use case to share.

However, if I were in a situation where a company needed a data integration platform, I would consider recommending SeaTunnel depending on the requirements.

For example, if the company needs to connect many different data sources and sinks and needs distributed execution for ETL or ELT workloads, SeaTunnel could be a good option.

Of course, I would also consider the trade-offs carefully. The decision should depend on the company’s data volume, reliability requirements, operational cost, and whether SeaTunnel’s connector ecosystem matches the company’s needs.

  1. What kind of support or growth opportunities do you hope continued participation in the SeaTunnel community can provide for your personal development?

Through continued participation in the SeaTunnel community, I hope to grow both technically and personally.

Technically, I want to deepen my understanding of data integration systems,
distributed systems, checkpointing, failure recovery, connector design, and
engine architecture.

I also hope to improve my communication skills. By discussing technical topics with community members, reviewing pull requests, and receiving feedback from experienced contributors, I have been able to learn a lot.

In addition, I want to improve my English communication skills. For example, participating in events such as ApacheCon, listening to technical talks, and giving presentations would be very valuable experiences for me.

Overall, the SeaTunnel community gives me opportunities to grow not only as a developer but also as a person who can communicate, collaborate, and contribute in an international open-source community.

  1. What is your understanding of the Committer role within the community? What responsibilities and impact should a Committer have?

In my understanding, a Committer can contribute to the community in many ways, not only by writing code.

A Committer can review pull requests, help maintain code quality, guide contributors, and help new contributors become more familiar with the project.

I also think a Committer should regularly think about what actions can have a positive impact on the community. This includes giving constructive feedback, helping discussions move forward, and making decisions that are good for the
long-term health of the project.

So I believe the Committer role is not just a permission to merge code. It is also a responsibility to help the project and the community grow in a healthy direction.

  1. Now that you have been elected as a Committer, do you have any thoughts you would like to share with the community, or suggestions for the future development of the project?

I am very grateful to be elected as an Apache SeaTunnel Committer.

While participating in the community, I have gained many valuable experiences. I am happy that my passion and contributions could be helpful to the community.

I would like to thank everyone who reviewed my pull requests, answered my questions, and discussed technical topics with me. Their feedback and support helped me continue contributing to the project.

There were some difficult moments, but I think all of those experiences became part of my growth.

At the moment, I do not have a specific proposal for the future direction of the
project. However, if I find areas that could be improved, I will continue to share my thoughts through GitHub issues, pull requests, and community discussions.

  1. What are your personal plans for contributing to and promoting the further development of the community and project in the near future?

In the near future, I would like to continue helping contributors so that they
can contribute to SeaTunnel more easily.

One way I can do this is through pull request reviews. I want to continue reviewing PRs, giving feedback, and helping contributors understand the project better.

I am also interested in helping more people in the Korean open-source community learn about SeaTunnel and contribute to the project. I think this could help both new contributors and the SeaTunnel community.

In addition, I plan to continue sharing my experiences through platforms such as LinkedIn and Medium. By writing about SeaTunnel, my contribution experience, and technical problems I have worked on, I hope more people can become interested in the project.

Top comments (0)