Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Translate this passage #8801

Open
3 tasks done
Gemini147258 opened this issue Feb 24, 2025 · 1 comment
Open
3 tasks done

[Feature] Translate this passage #8801

Gemini147258 opened this issue Feb 24, 2025 · 1 comment

Comments

@Gemini147258
Copy link

Search before asking

  • I had searched in the feature and found no similar feature requirement.

Description

Rich and extensible Connector: SeaTunnel provides a Connector API that does not depend on a specific execution engine. Connectors (Source, Transform, Sink) developed based on this API can run on many different engines, such as SeaTunnel Engine(Zeta), Flink, and Spark.
Connector plugin: The plugin design allows users to easily develop their own Connector and integrate it into the SeaTunnel project. Currently, SeaTunnel supports more than 100 Connectors, and the number is surging.
Batch-stream integration: Connectors developed based on the SeaTunnel Connector API are perfectly compatible with offline synchronization, real-time synchronization, full-synchronization, incremental synchronization and other scenarios. They greatly reduce the difficulty of managing data integration tasks.
Supports a distributed snapshot algorithm to ensure data consistency.
Multi-engine support: SeaTunnel uses the SeaTunnel Engine(Zeta) for data synchronization by default. SeaTunnel also supports the use of Flink or Spark as the execution engine of the Connector to adapt to the enterprise's existing technical components. SeaTunnel supports multiple versions of Spark and Flink.
JDBC multiplexing, database log multi-table parsing: SeaTunnel supports multi-table or whole database synchronization, which solves the problem of over-JDBC connections; and supports multi-table or whole database log reading and parsing, which solves the need for CDC multi-table synchronization scenarios to deal with problems with repeated reading and parsing of logs.
High throughput and low latency: SeaTunnel supports parallel reading and writing, providing stable and reliable data synchronization capabilities with high throughput and low latency.
Perfect real-time monitoring: SeaTunnel supports detailed monitoring information of each step in the data synchronization process, allowing users to easily understand the number of data, data size, QPS and other information read and written by the synchronization task.
Two job development methods are supported: coding and canvas design. The SeaTunnel web project https://github.com/apache/seatunnel-web provides visual management of jobs, scheduling, running and monitoring capabilities.

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Gemini147258
Copy link
Author

丰富且可扩展的 Connector:SeaTunnel 提供了一个不依赖特定执行引擎的 Connector API。基于此 API 开发的连接器(Source、Transform、Sink)可以运行在许多不同的引擎上,例如 SeaTunnel Engine(Zeta)、Flink 和 Spark。
Connector 插件:插件设计允许用户轻松开发自己的 Connector 并将其集成到 SeaTunnel 项目中。目前,SeaTunnel 支持 100 多个连接器,而且数量还在激增。
批量流集成:基于 SeaTunnel Connector API 开发的连接器,完美兼容离线同步、实时同步、全量同步、增量同步等场景。它们大大降低了管理数据集成任务的难度。
支持分布式快照算法,保证数据一致性。
多引擎支持:SeaTunnel 默认使用 SeaTunnel Engine(Zeta) 进行数据同步。SeaTunnel 还支持使用 Flink 或 Spark 作为 Connector 的执行引擎,以适应企业现有的技术组件。SeaTunnel 支持 Spark 和 Flink 的多个版本。
JDBC 多路复用,数据库日志多表解析:SeaTunnel 支持多表或全库同步,解决了 JDBC 连接过度的问题;并支持多表或全库日志读取解析,解决了 CDC 多表同步场景处理日志重复读取解析问题的需求。
高吞吐低时延:SeaTunnel 支持并行读写,提供稳定可靠的高吞吐、低时延数据同步能力。
完善的实时监控:SeaTunnel 支持数据同步过程中每个步骤的详细监控信息,让用户轻松了解同步任务读写的数据数量、数据大小、QPS 等信息。
支持两种作业开发方法:编码和画布设计。SeaTunnel Web 项目 https://github.com/apache/seatunnel-web 提供作业的可视化管理、调度、运行和监控功能。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant