Search before asking

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

Description

Background​​
Apache InLong is a one-stop data integration framework that supports efficient streaming/batch data collection, aggregation, and distribution from diverse sources.

Apache InLong primarily focuses on ultra-large-scale data integration but lacks support for diverse data sources. In contrast, SeaTunnel provides extensive data source compatibility. By adding an ​​InLong Sink Connector​​ to SeaTunnel, users can reuse SeaTunnel's rich data sources to feed data into InLong, bridging the gap between versatile data ingestion and large-scale integration capabilities, and gain seamless integration with the InLong ecosystem, enhancing real-time data pipeline capabilities for scenarios like log/metrics synchronization and multi-system data distribution.

​​Proposal​​
Implement an Apache InLong Connector for SeaTunnel with the following features:

• ​​InLong Sink Connector​​: Write processed data to InLong clusters for downstream consumption or governance.
• Support core InLong configurations (e.g., groupId, streamId, authentication).

​​Module Structure​​

• Create a new module: seatunnel-connectors/connector-inlong, referencing existing message queue connectors (e.g., Pulsar).
• Leverage the InLong Java SDK (e.g., inlong-sdk-java) or direct API calls.

Usage Scenario

Distributing SeaTunnel-processed results through InLong to downstream systems (e.g., real-time dashboards, risk engines).
Suggested Solution

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct