[
https://issues.apache.org/jira/browse/BEAM-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123305#comment-17123305
]
Beam JIRA Bot commented on BEAM-4557:
-------------------------------------
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.
> Propagate keyed-ness of PValues properly in ReferenceRunner
> -----------------------------------------------------------
>
> Key: BEAM-4557
> URL: https://issues.apache.org/jira/browse/BEAM-4557
> Project: Beam
> Issue Type: Bug
> Components: runner-direct
> Reporter: Eugene Kirpichov
> Priority: P2
> Labels: stale-P2
>
> ULR, just like regular direct runner, needs to respect "keyed"-ness of
> certain PValues, for two purposes: 1) invoking transforms of those PValues
> serially per key (e.g. because some of such transform evaluators, such as
> GABW, are not thread-safe per key), and 2) supporting state and timers.
> In [https://github.com/apache/beam/pull/5585,] one of the commits adds such
> tracking, but only naively - directly on the outputs of GBKO and GABW,
> without propagating downstream through key-preserving DoFn's.
> This Jira is to mimic the behavior of KeyedPValueTrackingVisitor in ULR.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
