[BEAM-10303] FnApiDoFnRunner window observing optimization

• Type: Improvement
• Status: Resolved
• Priority: P3
• Resolution: Fixed
• Fix Version/s: Missing
• Component/s: sdk-java-harness
• Labels: Clarified portability
• Assignee: Luke Cwik
• Reporter: Luke Cwik
• Created: 22/Jun/20 22:46
• Updated: 13/Jan/22 21:49
• Resolved: 12/Jan/22 04:28

Description

Currently the FnApiDoFnRunner processes each element within it's own window. There is an easy optimization where we process the element once if and only if the function doesn't observe the window (either directly or indirectly via side inputs/state/...).

Issue Links

• is cloned by: BEAM-10420 PerWindowInvoker to handle window observing SplittableDoFns
• links to: GitHub Pull Request #12093
• links to: GitHub Pull Request #12419
• links to: GitHub Pull Request #12430
• links to: GitHub Pull Request #12710