dybyte opened a new pull request, #9920:
URL: https://github.com/apache/seatunnel/pull/9920
### Purpose of this pull request
- Introduce a new configuration option `physical-dag-enabled` that allows
users to control whether the engine generates and executes a physical DAG
(optimized for execution), or uses the logical DAG as defined in the
configuration.
- Fix a bug in pipeline lookup logic where key comparison used different
types, which could cause failures when mapping logical DAG vertices to
pipelines.
### Does this PR introduce _any_ user-facing change?
Yes. Users can now use the new configuration option `physical-dag-enabled`
to control DAG execution mode.
The default value maintains backward compatibility.
### How was this patch tested?
I verified that `JobDAGInfo` outputs differ between `physical-dag-enabled =
true` and `physical-dag-enabled = false` with a new test case.
### 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)
* [x] If necessary, please update the documentation to describe the new
feature. https://github.com/apache/seatunnel/tree/dev/docs
* [ ] 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]
