This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/31081 [Failing Test]:
ht
> To implement retraction (at least to do so efficiently) I think
you'll want it integrated in the model. e.g. for combiners one would
want to add the option to subtract values, otherwise you would end up
having to store every element defeating the performance that combiners
provide.
I think
I think there is more to it than that. You'll probably want retractions
integrated into Beam's core triggering.
One example of where retractions are needed is with session windows. Early
triggers are fairly broken with session windows because the windows
themselves change as more data arrive. So a
There's at least one breaking change that should be reverted for this
release [1], so I'm going to close voting on RC1 and move to an RC2 once
the fix is merged.
Thanks,
Danny
[1] https://github.com/apache/beam/pull/31109
On Wed, Apr 24, 2024 at 11:17 PM XQ Hu wrote:
> +1 (non binding). Tested
