beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Knowles (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (BEAM-24) Merging of watermark holds depends on runner-specific "take the minimum" behavior
Date Fri, 19 Feb 2016 21:43:18 GMT

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

Kenneth Knowles reassigned BEAM-24:
-----------------------------------

    Assignee: Kenneth Knowles  (was: Frances Perry)

> Merging of watermark holds depends on runner-specific "take the minimum" behavior
> ---------------------------------------------------------------------------------
>
>                 Key: BEAM-24
>                 URL: https://issues.apache.org/jira/browse/BEAM-24
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>
> When multiple watermark holds are to be combined via an OutputTimeFn and committed to
persistent storage, the case where the OutputTimeFn computes the minimum is elided, assuming
the underlying runner will perform this combine by default.
> This is a natural default, but today it is a runner-specific behavior that the runner-agnostic
code relies upon.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message