Friendly reminder: Feb 3rd is the latest day to record GSoC 2024 project
ideas. There are no Beam projects in the list at the moment.
If you have an idea and you need help, please feel free to ask your
questions here.
On Fri, Jan 26, 2024 at 12:12 PM Ahmet Altay wrote:
> Hi all!
>
> GSoC is a g
Something went wrong during the automatic credentials rotation for Metrics
Cluster, performed at 2024-02-01. It may be necessary to check the state of the
cluster certificates. For further details refer to the following links:\n *
Failing job:
https://github.com/apache/beam/actions/workflows/be
Hi y'all,
I still exist!
I saw this and figured others could find it interesting -
https://github.com/timeplus-io/proton
Best
-P.
On Wed, Jan 31, 2024 at 4:21 AM Jan Lukavský wrote:
> Hi,
>
> if I understand this proposal correctly, the motivation is actually
> reducing latency by bypassing bundle atomic guarantees, bundles after "at
> least once" Reshuffle would be reconstructed independently of the
> pre-shuffle bundling.
On Tue, Jan 30, 2024 at 5:22 PM Robert Burke wrote:
> Is the benefit of this proposal just the bounded deviation from the
> existing reshuffle?
>
> Reshuffle is already rather dictated by arbitrary runner choice, from
> simply ignoring the node, to forcing a materialization break, to a full
> shu
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/30159 [Failing Test]: Pos
Hi,
if I understand this proposal correctly, the motivation is actually
reducing latency by bypassing bundle atomic guarantees, bundles after
"at least once" Reshuffle would be reconstructed independently of the
pre-shuffle bundling. Provided this is correct, it seems that the
behavior is sli
