[
https://issues.apache.org/jira/browse/BEAM-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132190#comment-17132190
]
Beam JIRA Bot commented on BEAM-24:
-----------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
>
> 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
(v8.3.4#803005)
