BenJFan opened a new issue, #1669:
URL: https://github.com/apache/incubator-seatunnel/issues/1669

   ### Search before asking
   
   - [X] I had searched in the 
[feature](https://github.com/apache/incubator-seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22)
 and found no similar feature requirement.
   
   
   ### Description
   
   Now all the connector jar in the binary distribution package of Seatunnel 
are packaged into one jar file: core . This makes it impossible for us to 
implement multi-version support for the same component.
   ### Now
   ```
   .
   apache-seatunnel
   | - - lib
         | - - seatunnel-core-spark.jar
         | - - seatunnel-core-flink.jar
   | - - plugins
   | - - config
   | - - bin
   ```
   ### After (Example for mulit-version Elasticsearch 6.x and 7.x)
   ```
   .
   apache-seatunnel
   | - - lib
         | - - seatunnel-core-spark.jar
         | - - seatunnel-core-flink.jar
   | - - connectors
         | - - flink
               | - - seatunnel-connector-flink-elasticsearch7.jar
               | - - seatunnel-connector-flink-kafka0.10.jar
               | - - other-all-lasted-version-connecotr-single.jar
         | - - spark
   | - - opt
         | - - flink
               | - - seatunnel-connector-flink-elasticsearch6.jar
               | - - seatunnel-connector-flink-kafka0.08.jar
               | - - other-all-older-version-connecotr-single.jar
         | - - spark            
   | - - plugins
   | - - config
   | - - bin
   ```
   After this finish, user can use differcult version connecotor on one release 
version, just need move jar from opt folder to connectors folder.
   
   ### Usage Scenario
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to