1996fanrui opened a new pull request, #23303:
URL: https://github.com/apache/flink/pull/23303

   ## What is the purpose of the change
   
   [FLINK-1285](https://issues.apache.org/jira/browse/FLINK-1285) updated the 
MutableObjectMode to ObjectReuse. The TaskConfig#getMutableObjectMode() is not 
used for a long long time, and it's internal class, so it can be removed 
directly.
   
   Also, we should update the GroupReduceDriverTest:
   
   - Updating the testAllReduceDriverAccumulatingImmutable() from 
`context.setMutableObjectMode(false);` to 
`context.getExecutionConfig().disableObjectReuse();`.
   - Updating the testAllReduceDriverIncorrectlyAccumulatingMutable() to 
`context.getExecutionConfig().disableObjectReuse();`, and fix the assert.
   
    
   More details can be get from 
https://github.com/apache/flink/pull/23233#discussion_r1304595960
   
   
   ## Brief change log
   
   - [FLINK-32847][flink-runtime] Removing the deprecated MutableObjectMode and 
restore related tests
   - [FLINK-32847][flink-runtime][hotfix] Refactor some code with code style 
warning
   
   
   ## Verifying this change
   
   Improve the old tests:
   
   - GroupReduceDriverTest#testAllReduceDriverIncorrectlyAccumulatingMutable
   - GroupReduceDriverTest#testAllReduceDriverAccumulatingImmutable
   
   ## 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, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
   


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