apache-seatunnel-incubating-2.3.1源码

# Purpose This article introduces the new interface and the new code structure on account of the newly designed API for Connectors in Apache SeaTunnel. This helps developers quickly understand API and transformation layer improvements. On the other hand, it can guide contributors how to use the new API to develop new connectors.See this [issue](https://github.com/apache/incubator-seatunnel/issues/1608) for details. ## **Code Structure** In order to separate from the old code, we have defined new modules for execution flow. This facilitates parallel development at the current stage, and reduces the difficulty of merging. ### engineering structure - ../`seatunnel-connectors-v2` connector-v2 code implementation - ../`seatunnel-translation` translation layer for the connector-v2 - ../`seatunnel-transform-v2` transform v2 connector implementation - ../seatunnel-e2e/`seatunnel-connector-v2-e2e` connector v2 e2e code - ../seatunnel-e2e/`seatunnel-flink-connector-v2-e2e` Obsolete, replaced by seatunnel-connector-v2-e2e - ../seatunnel-e2e/`seatunnel-spark-connector-v2-e2e` Obsolete, replaced by seatunnel-connector-v2-e2e - ../seatunnel-examples/`seatunnel-flink-connector-v2-example` seatunnel connector-v2 example use flink local running instance - ../seatunnel-examples/`seatunnel-spark-connector-v2-example` seatunnel connector-v2 example use spark local running instance ### **Example** We have prepared two new version of the locally executable example program in `seatunnel-examples`,one is `seatunnel-examples/seatunnel-flink-connector-v2-example/src/main/java/org/apache/seatunnel/example/flink/v2/SeaTunnelApiExample.java` , it runs in the Flink engine. Another one is `seatunnel-examples/seatunnel-spark-connector-v2-example/src/main/java/org/apache/seatunnel/example/spark/v2/SeaTunnelApiExample.java` , it runs in the Spark engine. This is also the debugging method that is often used in the local development of Connector. You can debug these examples, which will help you better understand the running logic of the program. The configuration files used in example are saved in the "resources/examples" folder. If you want to add examples for your own connectors, you need to follow the steps below. 1. Add the groupId, artifactId and version of the connector to be tested to `seatunnel-examples/seatunnel-flink-connector-v2-example/pom.xml`(or add it to `seatunnel-examples/seatunnel-spark-connector-v2-example/pom.xml` when you want to runs it in Spark engine) as a dependency. 2. Find the dependency in your connector pom file which scope is test or provided and then add them to seatunnel-examples/seatunnel-flink-connector-v2-example/pom.xml(or add it to seatunnel-examples/seatunnel-spark-connector-v2-example/pom.xml) file and modify the scope to compile. 3. Add the task configuration file under resources/examples. 4. Configure the file in the `SeaTunnelApiExample` main method. 5. Just run the main method. ### **Create new seatunnel v2 connector** 1.Create a new module under the `seatunnel-connectors-v2` directory and name it connector - {connector name}. 2.The pom file can refer to the pom file of the existing connector, and add the current sub model to the pom file of the parent model 3.Create two packages corresponding to source and sink ​ package org.apache.seatunnel.connectors.seatunnel.{connector name}}.source ​ package org.apache.seatunnel.connectors.seatunnel.{connector name}}.sink 4.add connector info to plugin-mapping.properties file in seatunnel root path. 5.add connector dependency to seatunnel-dist/pom.xml, so the connector jar can be find in binary package. ### **Startup Class** Aside from the old startup class, we have created two new startup modules, namely ``seatunnel-core/seatunnel-flink-starter`` and ``seatunnel-core/seatunnel-spark-starter``. You can find out how to parse the configuration file into an executable Flink/Spark process here. ### **SeaTunnel API** A new ``seatunnel-api`` (not ``seatunnel-apis``) module has been created to store the new interfaces defined by the SeaTunnel API. By implementing these interfaces, developers can complete the SeaTunnel Connector that supports multiple engines. ### **Translation Layer** We realize the conversion between SeaTunnel API and Engine API by adapting the interfaces of different engines, so as to achieve the effect of translation, and let our SeaTunnel Connector support the operation of multiple different engines. The corresponding code address, ``seatunnel-translation``, this module has the corresponding translation layer implementation. If you are interested, you can view the code and help us improve the current code. ## **API introduction** The API design of the current version of SeaTunnel draws on the design concept of Flink. ### **Source** #### **SeaTunnelSource.java** - The Source of SeaTunnel adopts the design of stream-batch integration, ``getBoundedness`` which determines whether the current Source is a stream Source or a batch Source, so you can specify a Source by dynamic configuration (refer to the default method), which can be either a stream or a batch. - ``getRowTypeInfo`` To get the schema of the data, the connector can choose to hard-code to implement a fixed schema, or run the user to customize the schema through config configuration. The latter is recommended. - SeaTunnelSource is a class executed on the driver side, through which objects such as SourceReader, SplitEnumerator and serializers are obtained. - Currently, the data type supported by SeaTunnelSource must be SeaTunnelRow. #### **SourceSplitEnumerator.java** Use this enumerator to get the data read shard (SourceSplit) situation, different shards may be assigned to different SourceReaders to read data. Contains several key methods: - ``run``: Used to perform a spawn SourceSplit and call ``SourceSplitEnumerator.Context.assignSplit``: to distribute the shards to the SourceReader. - ``addSplitsBackSourceSplitEnumerator``: is required to redistribute these Splits when SourceSplit cannot be processed normally or restarted due to the exception of SourceReader. - ``registerReaderProcess``: some SourceReaders that are registered after the run is run. If there is no SourceSplit distributed at this time, it can be distributed to these new readers (yes, you need to maintain your SourceSplit distribution in SourceSplitEnumerator most of the time). - ``handleSplitRequest``: If some Readers actively request SourceSplit from SourceSplitEnumerator, this method can be called SourceSplitEnumerator.Context.assignSplit to sends shards to the corresponding Reader. - ``snapshotState``: It is used for stream processing to periodically return the current state that needs to be saved. If there is a state restoration, it will be called SeaTunnelSource.restoreEnumerator to constructs a SourceSplitEnumerator and restore the saved state to the SourceSplitEnumerator. - ``notifyCheckpointComplete``: It is used for subsequent processing after the state is successfully saved, and can be used to store the state or mark in third-party storage. #### **SourceSplit.java** The interface used to save shards. Different shards need to define different splitIds. You can implement this interface to save the data that shards need to save, such as kafka's partition and topic, hbase's columnfamily and other information, which are used by SourceReader to determine Which part of the total data should be read. #### **SourceReader.java** The interface that directly interacts with the data source, and the action of reading data from the data source is completed by implementing this interface. - ``pollNext``: It is the core of Reader. Through this interface, the process of reading the data of the data source a