[Issue 3] Apache SeaTunnel(Incubating) Weekly FAQ

3 min readApr 27, 2023

April 15th — April 21st

Q: Does the checkpoint support cold start at present? Like specifying Checkpoint when restarting, similar to Flink recovering from Checkpoint.
A: Yes, you can start from the last checkpoint by adding the -r parameter when starting.

Q: Is there any comparison between the Flink engine and the SeaTunnel 2.3.1 Zeta engine?
A: Search “zeta” in the Wechat account SeaTunnel, and you can find articles about this.

Q: If multiple sources are not supported, how to synchronize the MySQL sub-database and sub-table? With multiple tasks?
A: You can configure multiple sources and multiple sinks in one task, and then use source_table_name and result_table_name to correspond one-to-one.

Q: About SeaTunnel Sink, is there any configuration for inserting timestamps?
A: SQL transform already support this functionality.

Q: How to submit tasks to the Flink cluster?
A: Just submit it to jobmanager.

Q: The iceberg sink is not supported now, is there any plan to support it?
A: Yes, and the community is welcome to contribute.

Q: Can SeaTunnel 2.3.1 use the native Spark SQL function?
A: No.

Q: Does SeaTunnel support offline whole library synchronization?
A: You can choose the batch mode of CDC for whole library synchronization.

Q: Can SeaTunnel use MySQL 5 and 8 at the same time?
A: In theory, it should be possible to read MySQL 5 data with the MySQL 8 driver.

Q: How to deal with the inconsistency between the fields in the source and the sink? Can I directly rename as in the source?
A: Yes, you can also use SQL Transform or FilterMapper Transform to rename.

📌📌Welcome to fill out this survey to give your feedback on your user experience or just your ideas about Apache SeaTunnel:)

About Apache SeaTunnel

Apache SeaTunnel (formerly Waterdrop) is an easy-to-use, ultra-high-performance distributed data integration platform that supports real-time synchronization of massive amounts of data and can synchronize hundreds of billions of data per day in a stable and efficient manner.

Why do we need Apache SeaTunnel?

Apache SeaTunnel does everything it can to solve the problems you may encounter in synchronizing massive amounts of data.

Data loss and duplication
Task buildup and latency
Low throughput
Long application-to-production cycle time
Lack of application status monitoring

Apache SeaTunnel Usage Scenarios

Massive data synchronization
Massive data integration
ETL of large volumes of data
Massive data aggregation
Multi-source data processing

Features of Apache SeaTunnel

Rich components
High scalability
Easy to use
Mature and stable

How to get started with Apache SeaTunnel quickly?

Want to experience Apache SeaTunnel quickly? SeaTunnel 2.1.0 takes 10 seconds to get you up and running.

https://seatunnel.apache.org/docs/2.1.0/developement/setup

How can I contribute?

We invite all partners who are interested in making local open-source global to join the Apache SeaTunnel contributors family and foster open-source together!

Submit an issue:

https://github.com/apache/incubator-seatunnel/issues

Contribute code to:

https://github.com/apache/incubator-seatunnel/pulls

Subscribe to the community development mailing list :

dev-subscribe@seatunnel.apache.org

Development Mailing List :

dev@seatunnel.apache.org

Join Slack:

https://join.slack.com/t/apacheseatunnel/shared_invite/zt-1kcxzyrxz-lKcF3BAyzHEmpcc4OSaCjQ

Follow Twitter:

https://twitter.com/ASFSeaTunnel