[
https://issues.apache.org/jira/browse/BEAM-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Knowles updated BEAM-260:
---------------------------------
Summary: WindowMappingFn: Know the getSideInputWindow upper bound to
release side input resources (was: Know the getSideInputWindow upper bound so
can gc side input state)
> WindowMappingFn: Know the getSideInputWindow upper bound to release side
> input resources
> ----------------------------------------------------------------------------------------
>
> Key: BEAM-260
> URL: https://issues.apache.org/jira/browse/BEAM-260
> Project: Beam
> Issue Type: Bug
> Components: beam-model, beam-model-runner-api
> Reporter: Mark Shields
> Assignee: Kenneth Knowles
>
> We currently have no static knowledge about the getSideInputWindow function,
> and runners are thus forced to hold on to all side input state / elements in
> case a future element reaches back into an earlier side input element.
> Maybe we need an upper bound on lag from current to result of
> getSideInputWindow so we can have a progressing gc horizon as we do for GKB
> window state.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
