gaoyunhaii opened a new pull request #10018: [FLINK-14521][DataStream] Fix the colocation issues when the operatoris chained with others URL: https://github.com/apache/flink/pull/10018 ## What is the purpose of the change This PR tries to fix the issues when the operator is chained with other operators. Currently when create operator chain, the colocation group configuration is not considered, and for a tree of chained operators, the colocation group configured with the root operator is always used. Therefore, if an operator except for the root one has configured with the colocation group, it will always be ignored, this will cause some colocation configuration does not take effect. ## Brief change log - 3f6588fd45ff1fd13c9798974c8d34d143215da0 has changed the logic to test whether an operator can be chained with its precedent to consider the colocation configuration. The operator can only be chained if it's colocation configuration does not conflict with the other operators in chain. Besides, the colocation group is always set to the right one of each chain for the resulting job vertex. ## Verifying this change This change added tests and can be verified as follows: - Added tests to ensure the colocation group is set correctly for each scenarios. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): **no** - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: **no** - The serializers: **no** - The runtime per-record code paths (performance sensitive): **no** - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: **no** - The S3 file system connector: **no** ## Documentation - Does this pull request introduce a new feature? **no** - If yes, how is the feature documented? **not applicable**
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
