JeremyXin opened a new issue, #11074:
URL: https://github.com/apache/seatunnel/issues/11074

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22bug%22)
 and found no similar issues.
   
   
   ### What happened
   
   For CI optimization, one potential problem was identified as follows.
   
   `seatunnel-translation-base` currently includes `connector-file-base` and 
`connector-doris` as test dependencies for ParallelSourceTest.
   
   This causes unrelated connector incremental IT jobs to pull these modules 
into the Maven reactor through the shared translation -> starter -> e2e 
dependency chain.
   
   As a result, changes in an unrelated connector such as 
`connector-elasticsearch-v2` may still trigger unnecessary build steps for 
`connector-file-base` or `connector-doris`, increasing CI cost and noise.
   
   The root cause is that connector-specific test dependencies were added to a 
shared base module. ParallelSourceTest should verify the common split 
assignment behavior without depending on concrete connector implementations.
   
   ### SeaTunnel Version
   
   2.3.13
   
   ### SeaTunnel Config
   
   ```conf
   None
   ```
   
   ### Running Command
   
   ```shell
   None
   ```
   
   ### Error Exception
   
   ```log
   None
   ```
   
   ### Zeta or Flink or Spark Version
   
   Zeta
   
   ### Java or Scala Version
   
   Java 1.8
   
   ### Screenshots
   
   <img width="2262" height="356" alt="Image" 
src="https://github.com/user-attachments/assets/cf7a5384-ad1e-4028-bed4-2f7d35135368";
 />
   
   ### Are you willing to submit 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