You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:51:03 UTC

[jira] [Updated] (BEAM-10303) FnApiDoFnRunner window observing optimization

     [ https://issues.apache.org/jira/browse/BEAM-10303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-10303:
-----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> FnApiDoFnRunner window observing optimization
> ---------------------------------------------
>
>                 Key: BEAM-10303
>                 URL: https://issues.apache.org/jira/browse/BEAM-10303
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-harness
>            Reporter: Luke Cwik
>            Priority: P3
>              Labels: Clarified, portability
>          Time Spent: 10.5h
>  Remaining Estimate: 0h
>
> 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/...).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)