LiJie20190102 opened a new pull request, #10431:
URL: https://github.com/apache/seatunnel/pull/10431

   <!--
   
   Thank you for contributing to SeaTunnel! Please make sure that your code 
changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   ## Contribution Checklist
     - Make sure that the pull request corresponds to a [GITHUB 
issue](https://github.com/apache/seatunnel/issues).
     - Name the pull request in the form "[Feature] [component] Title of the 
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
     - Minor fixes should be named following this pattern: `[hotfix] [docs] Fix 
typo in README.md doc`.
   -->
   
   ### Purpose of this pull request
   
   Implement feature #10167 
   
   
   ### Does this PR introduce _any_ user-facing change?
   
   <!--
   Note that it means *any* user-facing change including all aspects such as 
the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes 
- provide the console output, description and/or an example to show the 
behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to 
the released SeaTunnel versions or within the unreleased branches such as dev.
   If no, write 'No'.
   If you are adding/modifying connector documents, please follow our new 
specifications: https://github.com/apache/seatunnel/issues/4544.
   -->
   
   
   ### How was this patch tested?
   
   1、Deploy the master node and the slave node on the same machine, set ST_HOME 
to `/opt/soft/st0201/server`, and configure the network settings in 
`hazelcast-master.yaml` and `hazelcast-worker.yaml`
   2、Deploy the client on another server, with ST_HOME set to 
`/opt/soft/st0201/client`, and configure the network settings in 
`hazelcast-client.yaml`. This ensures that the package paths for the server and 
client are different. 
   3、Submit the task on the client side, such as `bin/seatunnel.sh --config 
config/v2.batch.config.template` . After submitting the task, check whether it 
is executed successfully, and ensure that the server logs do not contain any 
client file resources
   
   ### Self-test results
   - Before
      client log:
   <img width="1664" height="640" alt="image" 
src="https://github.com/user-attachments/assets/b5f3e1e5-3733-47f1-8bfe-ae909297d90a";
 />
     server master log:
    
   <img width="1675" height="645" alt="14B051F8C4C1DF729C55470778425E5E" 
src="https://github.com/user-attachments/assets/0cdf6808-e2f4-441e-b352-76d7b8dd6828";
 />
   - After
   client log:
   <img width="1676" height="595" alt="AA9CD784258FF87D3C18D08FCA0B2C6C" 
src="https://github.com/user-attachments/assets/5fd6132f-f539-45e9-be52-2e3d898be8cb";
 />
   server master log
   <img width="1684" height="708" alt="23FAECAA699F5B0839B9E896EFDEDB6D" 
src="https://github.com/user-attachments/assets/a23b6800-805e-48d2-85ca-1b774bc4c23d";
 />
   server worker log
   <img width="1594" height="514" alt="06A7B960FF59587217B06CA80B8D38D7" 
src="https://github.com/user-attachments/assets/9b835196-0561-49bb-84aa-86fbedf185ec";
 />
   
   
   ### Check list
   
   * [ ] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/contribution/new-license.md)
   * [ ] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [ ] If necessary, please update `incompatible-changes.md` to describe the 
incompatibility caused by this PR.
   * [ ] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/seatunnel-connector-v2-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)


-- 
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