+1 (binding)
Tested Flink Runner with java SDK.
Jan
On 10/16/24 01:35, Valentyn Tymofieiev via dev wrote:
+1 (binding), checked dataflow containers and ran a few Python pipelines.
On Tue, Oct 15, 2024 at 4:22 PM Ahmet Altay via dev
wrote:
+1 (binding)
On Tue, Oct 15, 2024 at 4:1
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/32794 The PostCommit Pyth
+1 (non-binding)
Tested DataflowTemplates integration test (
https://github.com/GoogleCloudPlatform/DataflowTemplates/pull/1938). Also
tested Java+Python Quickstart+mobile game walkthrough on Direct runner and
Dataflow runner.
On Wed, Oct 16, 2024 at 3:45 AM Jan Lukavský wrote:
> +1 (binding)
>
Hi everyone,
I would like to volunteer to rerelease the Beam vendored grpc 1.60.1. The
grpc version will be unchanged but protobuf sources will be excluded from
the jar, addressing [1].
My plan is to follow the release process [2, 3], which involves preparing
for the release, building a candidat
Thanks a lot, Yi!
On Wed, Oct 16, 2024 at 3:25 PM Yi Hu via dev wrote:
> Hi everyone,
>
> I would like to volunteer to rerelease the Beam vendored grpc 1.60.1. The
> grpc version will be unchanged but protobuf sources will be excluded from
> the jar, addressing [1].
>
> My plan is to follow the
HI @Yi Hu - Do you know the answer to this question? And
if it is not vendored, should it be?
On Wed, Oct 9, 2024 at 5:17 PM XQ Hu wrote:
> I do not think ANLTR is vendored. +Yi here.
>
> On Wed, Oct 9, 2024 at 4:35 PM Reuven Lax wrote:
>
>> Is our usage of ANLTR not vendored?
>>
>> On Wed, Oc
Thanks for catching these. Checked that
> Prism artifacts as the Github Release wasn't published or updated with
the latest RC tag.
was due to
https://github.com/apache/beam/actions/runs/11321090196
failed to stage prism. Rerun the workflow and the issue resolved.
> It's also missing the blog
Hi all,
As the Beam ML and Beam YAML frameworks and communities continue to grow,
there is a great opportunity to link these two together by introducing ML
capabilities to Beam YAML. By integrating ML capabilities into Beam YAML,
we can dramatically simplify the development and deployment of machi
I inspected the java core artifact and confirm that Beam's usage of antlr
is vendored, in principle it should not leak antlr runtime class
dependencies.
Specifically, I checked that only java-core used antlr, and the classes are
relocated:
https://github.com/apache/beam/blob/1e279788027ffa031f634a
+1 (binding)
I have validated the prism release artifacts for linux-amd64, and that they
work with the Python and Java SDK starters.
I've also looked over and found a typo in the 2.60.0 blog post.
Thanks Yi!
Robert Burke
On 2024/10/16 17:47:51 Yi Hu via dev wrote:
> Thanks for catching these. C
-1 (binding) Unable to validate Prism artifacts as the Github Release wasn't
published or updated with the latest RC tag.
https://github.com/apache/beam/blob/master/contributor-docs/release-guide.md#update-the-github-release-with-the-blog-post-content
It looks like the RC1 github release page ex
11 matches
Mail list logo