beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Groh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BEAM-260) WindowMappingFn: Know the getSideInputWindow upper bound to release side input resources
Date Tue, 11 Apr 2017 17:43:45 GMT

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

Thomas Groh resolved BEAM-260.
------------------------------
       Resolution: Fixed
    Fix Version/s: First stable release

> 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-fn-api, beam-model-runner-api
>            Reporter: Mark Shields
>            Assignee: Thomas Groh
>             Fix For: First stable release
>
>
> 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.15#6346)

Mime
View raw message