codenohup opened a new pull request, #25706:
URL: https://github.com/apache/flink/pull/25706

   ## What is the purpose of the change
   
   Fix fix series bugs of DSv2.
   
   1. The DSv2 org.apache.flink.datastream.api.ExecutionEnvironment#fromSource 
method return a 
   NonKeyedPartitionStream, which does not allow users to set source 
configurations, such as operator name or parallelism.
   
   2. The org.apache.flink.datastream.api.context.TaskInfo lack subtaskIndex 
and attemptNumber.
   
   3. The open and close methods of 
org.apache.flink.datastream.api.function.ProcessFunction are not being called.
   
   4. The open method of 
org.apache.flink.datastream.api.function.ProcessFunction lacks relevant 
information, such as the current TaskInfo.
   
   ## Brief change log
   - Make ExecutionEnvironment#fromSource return 
ProcessConfigurableAndNonKeyedPartitionStream
   - Introduce subtask index and attempt id in TaskInfo for DSv2
   - Open and close user function in DSv2 ProcessOperator
   - Introduce a NonPartitionedContext parameter in Open method of UserFunction 
for DSv2
   
   
   ## Verifying this change
   
   This change is already covered by existing tests.
   
   ## 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)`: yes
     - 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
     - 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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to