[
https://issues.apache.org/jira/browse/BEAM-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15498458#comment-15498458
]
Aljoscha Krettek commented on BEAM-260:
---------------------------------------
The doc looks good, I'm not sure how many people will see this comment on a
Jira issue so it might make sense to [POPOSE] it on the ML.
> Know the getSideInputWindow upper bound so can gc side input state
> ------------------------------------------------------------------
>
> Key: BEAM-260
> URL: https://issues.apache.org/jira/browse/BEAM-260
> Project: Beam
> Issue Type: Bug
> Components: beam-model
> 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)
