Thanks. I added some comments to the doc.
I agree with Brian that it makes sense to figure out how this
interacts with batched DoFns, as we'll want to migrate to that.
(Perhaps they're already ready to migrate to as a first step?)
On Fri, Aug 12, 2022 at 1:03 PM Brian Hulette via dev
wrote:
>
>
+1 as well
(I believe Kiley is addressing the container tags issue)
Thanks,
Cham
On Mon, Aug 15, 2022 at 1:00 PM Robert Bradshaw wrote:
> +1 (binding).
>
> I verified the release artifacts and signatures, and ran a couple of
> simple Python pipelines.
>
> On Mon, Aug 15, 2022 at 12:40 PM
+1 (binding).
I verified the release artifacts and signatures, and ran a couple of
simple Python pipelines.
On Mon, Aug 15, 2022 at 12:40 PM Chamikara Jayalath via dev
wrote:
>
>
>
> On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok wrote:
>>
>> Thanks everyone!
>>
>> @Chamikara Jayalath The Spark
On Mon, Aug 15, 2022 at 11:37 AM Kiley Sok wrote:
> Thanks everyone!
>
> @Chamikara Jayalath The Spark issue is running
> successfully for me, could you try it again? I'll look into the container
> tags.
>
Thanks. Regarding the Spark issue, it could just be my setup then. Feel
free to close
Thanks everyone!
@Chamikara Jayalath The Spark issue is running
successfully for me, could you try it again? I'll look into the container
tags.
On Mon, Aug 15, 2022 at 11:04 AM Pablo Estrada wrote:
> +1 - I validated tests/build with existing Dataflow Templates
> Best
> -P.
>
> On Fri, Aug
+1 - I validated tests/build with existing Dataflow Templates
Best
-P.
On Fri, Aug 12, 2022 at 9:20 PM Ahmet Altay via dev
wrote:
> +1 - I validated python quickstarts on direct runner.
>
> Thank you Kiley!
>
>
>
> On Thu, Aug 11, 2022 at 9:56 PM Kiley Sok via dev
> wrote:
>
>> Hi everyone,
>>
I ran some validations and noticed the following.
* Dataflow Java/Python containers now have the suffix "rc1' while for the
previous releases I tested they used to have the same container ID as the
final release. I suspect this is just a process change for Dataflow.
* Spark quickstart keeps
Thanks for calling that out! I added a note that we're not using Jira
anymore to that page and removed some outdated information (including the
instructions to email the dev list). I kept the page around in case people
find it useful for interacting with resolved (non-migrated) issues or for
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/22642 [Bug]: Dataflow
