beyond1920 opened a new pull request #16521:
URL: https://github.com/apache/flink/pull/16521


   ## What is the purpose of the change
   
   In theory, `StreamPhysicalWindowTableFunction` should works as a window 
assigner and emits at ends of window. However, 
`StreamPhysicalWindowTableFunction` could be simplified to a simple window 
assigner, and emits per record if it's successor node is one of 
`WindowRank`/`WindowJoin`/`WindowAggregate` with 
`WindowAttachedWindowingStrategy`, because those nodes would assign input 
records to windows have been assigned in input nodes, and trigger emit at ends 
of window.
   
   Besides, we should add a limit that window is based on rowtime, because it 
has syntax problem if window is assigned based on the proc-time of previous 
operator.
   
   The pr aims to implement streaming window assigner tablefunction operator. 
   
   ## Brief change log
   
     - Introduce `WindowTableFunctionOperator` and 
`WindowTableFunctionOperatorTest`
     - Update `StreamExecWindowTableFunction` to handle some special case which 
satisfy: 1. emit record per record 2. use rowtime attribute
   
   
   ## Verifying this change
   
     - A harness test `WindowTableFunctionOperatorTest` to validate the 
behavior of `WindowTableFunctionOperator`
     - Add ITCases in `WindowJoinITCase` and `WindowRankITCase`
   
   ## 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)
     - 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