base on SeaTunnel is a next-generation super high-performance, distributed, massive data integration tool. # Apache SeaTunnel <img src="https://seatunnel.apache.org/image/logo.png" alt="SeaTunnel Logo" height="200px" align="right" /> [](https://github.com/apache/seatunnel/actions/workflows/build_main.yml) [](https://s.apache.org/seatunnel-slack) [](https://twitter.com/ASFSeaTunnel) ## Table of Contents - [Overview](#overview) - [Why Choose SeaTunnel](#why-choose-seatunnel) - [Key Features](#key-features) - [SeaTunnel Workflow](#seatunnel-workflow) - [Supported Connectors](#supported-connectors) - [Getting Started](#getting-started) - [Use Cases](#use-cases) - [Code of Conduct](#code-of-conduct) - [Contributors](#contributors) - [How to Compile](#how-to-compile) - [Contact Us](#contact-us) - [Landscapes](#landscapes) - [Apache SeaTunnel Web Project](#apache-seaTunnel-web-project) - [Our Users](#our-users) - [License](#license) - [Frequently Asked Questions](#frequently-asked-questions) ## Overview SeaTunnel is a next-generation, high-performance, distributed data integration tool, capable of synchronizing vast amounts of data daily. It's trusted by numerous companies for its efficiency and stability. ## Why Choose SeaTunnel SeaTunnel addresses common data integration challenges: - **Diverse Data Sources**: Seamlessly integrates with hundreds of evolving data sources. - **Complex Synchronization Scenarios**: Supports various synchronization methods, including real-time, CDC, and full database synchronization. - **Resource Efficiency**: Minimizes computing resources and JDBC connections for real-time synchronization. - **Quality and Monitoring**: Provides data quality and monitoring to prevent data loss or duplication. ## Key Features - **Diverse Connectors**: Offers support for over 100 connectors, with ongoing expansion. - **Batch-Stream Integration**: Easily adaptable connectors simplify data integration management. - **Distributed Snapshot Algorithm**: Ensures data consistency across synchronized data. - **Multi-Engine Support**: Works with SeaTunnel Zeta Engine, Flink, and Spark. - **JDBC Multiplexing and Log Parsing**: Efficiently synchronizes multi-tables and databases. - **High Throughput and Low Latency**: Provides high-throughput data synchronization with low latency. - **Real-Time Monitoring**: Offers detailed insights during synchronization. - **Two Job Development Methods**: Supports coding and visual job management with the [SeaTunnel Web Project](https://github.com/apache/seatunnel-web). ## SeaTunnel Workflow  Configure jobs, select execution engines, and parallelize data using Source Connectors. Easily develop and extend connectors to meet your needs. ## Supported Connectors - [Source Connectors](https://seatunnel.apache.org/docs/connector-v2/source) - [Sink Connectors](https://seatunnel.apache.org/docs/connector-v2/sink) - [Transform Connectors](docs/en/transform-v2) ## Getting Started Download SeaTunnel from the [Official Website](https://seatunnel.apache.org/download). Choose your runtime execution engine: - [SeaTunnel Zeta Engine](https://seatunnel.apache.org/docs/start-v2/locally/quick-start-seatunnel-engine/) - [Spark](https://seatunnel.apache.org/docs/start-v2/locally/quick-start-spark) - [Flink](https://seatunnel.apache.org/docs/start-v2/locally/quick-start-flink) ## Use Cases Explore real-world use cases of SeaTunnel, such as Weibo, Tencent Cloud, Sina, Sogou, and Yonghui Superstores. More use cases can be found on the [SeaTunnel Blog](https://seatunnel.apache.org/blog). ## Code of Conduct Participate in this project in accordance with the Contributor Covenant [Code of Conduct](https://www.apache.org/foundation/policies/conduct). ## Contributors We appreciate all developers for their contributions. See the [List Of Contributors](https://github.com/apache/seatunnel/graphs/contributors). ## How to Compile Refer to this [Setup](docs/en/contribution/setup.md) for compilation instructions. ## Contact Us - Mail list: **[email protected]**. Subscribe by sending an email to `[email protected]`. - Slack: [Join SeaTunnel Slack](https://s.apache.org/seatunnel-slack) - Twitter: [ASFSeaTunnel on Twitter](https://twitter.com/ASFSeaTunnel) ## Landscapes SeaTunnel enriches the [CNCF CLOUD NATIVE Landscape](https://landscape.cncf.io/?landscape=observability-and-analysis&license=apache-license-2-0). ## Apache SeaTunnel Web Project SeaTunnel Web is a web project that provides visual management of jobs, scheduling, running and monitoring capabilities. It is developed based on the SeaTunnel Connector API and the SeaTunnel Zeta Engine. It is a web project that can be deployed independently. It is also a sub-project of SeaTunnel. For more information, please refer to [SeaTunnel Web](https://github.com/apache/seatunnel-web) ## Our Users Companies and organizations worldwide use SeaTunnel for research, production, and commercial products. Visit our [Users](https://seatunnel.apache.org/user) for more information. ## License [Apache 2.0 License](LICENSE) ## Frequently Asked Questions ### 1. How do I install SeaTunnel? Follow the [Installation Guide](https://seatunnel.apache.org/docs/start-v2/locally/deployment/) on our website to get started. ### 2. How can I contribute to SeaTunnel? We welcome contributions! Please refer to our [Contribution Guidelines](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/coding-guide.md) for details. ### 3. How do I report issues or request features? You can report issues or request features on our [GitHub Repository](https://github.com/apache/seatunnel/issues). ### 4. Can I use SeaTunnel for commercial purposes? Yes, SeaTunnel is available under the Apache 2.0 License, allowing commercial use. ### 5. Where can I find documentation and tutorials? Our [Official Documentation](https://seatunnel.apache.org/docs) includes detailed guides and tutorials to help you get started. ### 6. Is there a community or support channel? Join our Slack community for support and discussions: [SeaTunnel Slack](https://s.apache.org/seatunnel-slack). More information, please refer to [FAQ](https://seatunnel.apache.org/docs/faq). ", Assign "at most 3 tags" to the expected json: {"id":"1091","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"