Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

[Chamikara Jayalath via dev]

Fix for the blocking issue was cherry-picked today. So I hope to build the
RC1 tomorrow.

Thanks,
Cham

On Thu, Nov 3, 2022 at 8:19 PM Ahmet Altay  wrote:

> How is the release coming along? Do you need any help?
>
> On Mon, Oct 31, 2022 at 1:58 PM Chamikara Jayalath via dev <
> dev@beam.apache.org> wrote:
>
>> Update:
>>
>> Hi All,
>>
>> I've been validating the release branch by running all Jenkins test
>> suites on it (as required by the release guide). This revealed two new
>> potential issues. I added these to the release milestone [1]. Please
>> comment on these issues if you are familiar with the errors (for example,
>> if they are known issues from a previous release). We can continue the
>> release once these are resolved or moved out of the 2.43.0 release
>> milestone.
>>
>> Thanks,
>> Cham
>>
>> [1] https://github.com/apache/beam/milestone/5
>>
>> On Wed, Oct 26, 2022 at 12:42 PM Chamikara Jayalath 
>> wrote:
>>
>>> Update:
>>>
>>> All blocking issues have either been addressed or pushed to the next
>>> release. I'll go ahead and create the first RC.
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Thu, Oct 20, 2022 at 9:41 AM Chamikara Jayalath 
>>> wrote:
>>>
 Hi All,

 The release branch was cut:
 https://github.com/apache/beam/tree/release-2.43.0

 We currently have three open blockers in the release milestone:
 https://github.com/apache/beam/milestone/5

 I'll look into cherry-picking fixes for these and hopefully creating a
 RC early next week.

 Thanks,
 Cham

 On Wed, Oct 5, 2022 at 3:25 PM Ahmet Altay  wrote:

> +1 - Thank you Cham!
>
> On Wed, Oct 5, 2022 at 1:38 PM Chamikara Jayalath via dev <
> dev@beam.apache.org> wrote:
>
>> Hi all,
>>
>> The next (2.43.0) release branch cut is scheduled for October 19th,
>> according to the release calendar [1].
>>
>> I would like to volunteer myself to do this release. My plan is to
>> cut the branch on that date, and cherrypick release-blocking fixes
>> afterwards, if any.
>>
>> Please help me make sure the release goes smoothly by:
>> - Making sure that any unresolved release blocking issues for 2.43.0 
>> should
>> have their "Milestone" marked as "2.43.0 Release" [2] as soon as
>> possible.
>> - Reviewing the current release blockers [2] and removing the
>> Milestone if they don't meet the criteria at [3].
>>
>> Let me know if you have any comments/objections/questions.
>>
>> Thanks,
>> Cham
>>
>> [1]
>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com
>> [2] https://github.com/apache/beam/milestone/5
>> [3] https://beam.apache.org/contribute/release-blocking/
>>
>

Re: [PROPOSAL] Preparing for Apache Beam 2.43.0 Release

[Ahmet Altay via dev]

How is the release coming along? Do you need any help?

On Mon, Oct 31, 2022 at 1:58 PM Chamikara Jayalath via dev <
dev@beam.apache.org> wrote:

> Update:
>
> Hi All,
>
> I've been validating the release branch by running all Jenkins test suites
> on it (as required by the release guide). This revealed two new
> potential issues. I added these to the release milestone [1]. Please
> comment on these issues if you are familiar with the errors (for example,
> if they are known issues from a previous release). We can continue the
> release once these are resolved or moved out of the 2.43.0 release
> milestone.
>
> Thanks,
> Cham
>
> [1] https://github.com/apache/beam/milestone/5
>
> On Wed, Oct 26, 2022 at 12:42 PM Chamikara Jayalath 
> wrote:
>
>> Update:
>>
>> All blocking issues have either been addressed or pushed to the next
>> release. I'll go ahead and create the first RC.
>>
>> Thanks,
>> Cham
>>
>> On Thu, Oct 20, 2022 at 9:41 AM Chamikara Jayalath 
>> wrote:
>>
>>> Hi All,
>>>
>>> The release branch was cut:
>>> https://github.com/apache/beam/tree/release-2.43.0
>>>
>>> We currently have three open blockers in the release milestone:
>>> https://github.com/apache/beam/milestone/5
>>>
>>> I'll look into cherry-picking fixes for these and hopefully creating a
>>> RC early next week.
>>>
>>> Thanks,
>>> Cham
>>>
>>> On Wed, Oct 5, 2022 at 3:25 PM Ahmet Altay  wrote:
>>>
 +1 - Thank you Cham!

 On Wed, Oct 5, 2022 at 1:38 PM Chamikara Jayalath via dev <
 dev@beam.apache.org> wrote:

> Hi all,
>
> The next (2.43.0) release branch cut is scheduled for October 19th,
> according to the release calendar [1].
>
> I would like to volunteer myself to do this release. My plan is to cut
> the branch on that date, and cherrypick release-blocking fixes afterwards,
> if any.
>
> Please help me make sure the release goes smoothly by:
> - Making sure that any unresolved release blocking issues for 2.43.0 
> should
> have their "Milestone" marked as "2.43.0 Release" [2] as soon as
> possible.
> - Reviewing the current release blockers [2] and removing the
> Milestone if they don't meet the criteria at [3].
>
> Let me know if you have any comments/objections/questions.
>
> Thanks,
> Cham
>
> [1]
> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com
> [2] https://github.com/apache/beam/milestone/5
> [3] https://beam.apache.org/contribute/release-blocking/
>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Danny McCormick via dev]

Congrats Ritesh! This is definitely well deserved!

On Thu, Nov 3, 2022 at 8:08 PM Robert Burke  wrote:

> Woohoo! Well done Ritesh! :D
>
> On Thu, Nov 3, 2022, 5:04 PM Anand Inguva via dev 
> wrote:
>
>> Congratulations Ritesh.
>>
>> On Thu, Nov 3, 2022 at 7:51 PM Yi Hu via dev  wrote:
>>
>>> Congratulations Ritesh!
>>>
>>> On Thu, Nov 3, 2022 at 7:23 PM Byron Ellis via dev 
>>> wrote:
>>>
 Congratulations!

 On Thu, Nov 3, 2022 at 4:21 PM Austin Bennett <
 whatwouldausti...@gmail.com> wrote:

> Congratulations, and Thanks @riteshgho...@apache.org!
>
> On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev <
> dev@beam.apache.org> wrote:
>
>> Congrats Ritesh!
>>
>> On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Ritesh Ghorse (riteshgho...@apache.org)
>>>
>>> Ritesh started contributing to Beam in mid-2021 and has contributed
>>> immensely to bringin the Go SDK to fruition, in addition to 
>>> contributions
>>> to Java and Python and release validation.
>>>
>>> Considering their contributions to the project over this timeframe,
>>> the Beam PMC trusts Ritesh with the responsibilities of a Beam 
>>> committer.
>>> [1]
>>>
>>> Thank you Ritesh! And we are looking to see more of your
>>> contributions!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>>
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Robert Burke]

Woohoo! Well done Ritesh! :D

On Thu, Nov 3, 2022, 5:04 PM Anand Inguva via dev 
wrote:

> Congratulations Ritesh.
>
> On Thu, Nov 3, 2022 at 7:51 PM Yi Hu via dev  wrote:
>
>> Congratulations Ritesh!
>>
>> On Thu, Nov 3, 2022 at 7:23 PM Byron Ellis via dev 
>> wrote:
>>
>>> Congratulations!
>>>
>>> On Thu, Nov 3, 2022 at 4:21 PM Austin Bennett <
>>> whatwouldausti...@gmail.com> wrote:
>>>
 Congratulations, and Thanks @riteshgho...@apache.org!

 On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev <
 dev@beam.apache.org> wrote:

> Congrats Ritesh!
>
> On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles 
> wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new
>> committer: Ritesh Ghorse (riteshgho...@apache.org)
>>
>> Ritesh started contributing to Beam in mid-2021 and has contributed
>> immensely to bringin the Go SDK to fruition, in addition to contributions
>> to Java and Python and release validation.
>>
>> Considering their contributions to the project over this timeframe,
>> the Beam PMC trusts Ritesh with the responsibilities of a Beam committer.
>> [1]
>>
>> Thank you Ritesh! And we are looking to see more of your
>> contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>>
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Anand Inguva via dev]

Congratulations Ritesh.

On Thu, Nov 3, 2022 at 7:51 PM Yi Hu via dev  wrote:

> Congratulations Ritesh!
>
> On Thu, Nov 3, 2022 at 7:23 PM Byron Ellis via dev 
> wrote:
>
>> Congratulations!
>>
>> On Thu, Nov 3, 2022 at 4:21 PM Austin Bennett <
>> whatwouldausti...@gmail.com> wrote:
>>
>>> Congratulations, and Thanks @riteshgho...@apache.org!
>>>
>>> On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev <
>>> dev@beam.apache.org> wrote:
>>>
 Congrats Ritesh!

 On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new
> committer: Ritesh Ghorse (riteshgho...@apache.org)
>
> Ritesh started contributing to Beam in mid-2021 and has contributed
> immensely to bringin the Go SDK to fruition, in addition to contributions
> to Java and Python and release validation.
>
> Considering their contributions to the project over this timeframe,
> the Beam PMC trusts Ritesh with the responsibilities of a Beam committer.
> [1]
>
> Thank you Ritesh! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Yi Hu via dev]

Congratulations Ritesh!

On Thu, Nov 3, 2022 at 7:23 PM Byron Ellis via dev 
wrote:

> Congratulations!
>
> On Thu, Nov 3, 2022 at 4:21 PM Austin Bennett 
> wrote:
>
>> Congratulations, and Thanks @riteshgho...@apache.org!
>>
>> On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Congrats Ritesh!
>>>
>>> On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles  wrote:
>>>
 Hi all,

 Please join me and the rest of the Beam PMC in welcoming a new
 committer: Ritesh Ghorse (riteshgho...@apache.org)

 Ritesh started contributing to Beam in mid-2021 and has contributed
 immensely to bringin the Go SDK to fruition, in addition to contributions
 to Java and Python and release validation.

 Considering their contributions to the project over this timeframe, the
 Beam PMC trusts Ritesh with the responsibilities of a Beam committer. [1]

 Thank you Ritesh! And we are looking to see more of your contributions!

 Kenn, on behalf of the Apache Beam PMC

 [1]

 https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer

>>>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Byron Ellis via dev]

Congratulations!

On Thu, Nov 3, 2022 at 4:21 PM Austin Bennett 
wrote:

> Congratulations, and Thanks @riteshgho...@apache.org!
>
> On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev 
> wrote:
>
>> Congrats Ritesh!
>>
>> On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles  wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Ritesh Ghorse (riteshgho...@apache.org)
>>>
>>> Ritesh started contributing to Beam in mid-2021 and has contributed
>>> immensely to bringin the Go SDK to fruition, in addition to contributions
>>> to Java and Python and release validation.
>>>
>>> Considering their contributions to the project over this timeframe, the
>>> Beam PMC trusts Ritesh with the responsibilities of a Beam committer. [1]
>>>
>>> Thank you Ritesh! And we are looking to see more of your contributions!
>>>
>>> Kenn, on behalf of the Apache Beam PMC
>>>
>>> [1]
>>>
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Austin Bennett]

Congratulations, and Thanks @riteshgho...@apache.org!

On Thu, Nov 3, 2022 at 4:17 PM Sachin Agarwal via dev 
wrote:

> Congrats Ritesh!
>
> On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles  wrote:
>
>> Hi all,
>>
>> Please join me and the rest of the Beam PMC in welcoming a new committer:
>> Ritesh Ghorse (riteshgho...@apache.org)
>>
>> Ritesh started contributing to Beam in mid-2021 and has contributed
>> immensely to bringin the Go SDK to fruition, in addition to contributions
>> to Java and Python and release validation.
>>
>> Considering their contributions to the project over this timeframe, the
>> Beam PMC trusts Ritesh with the responsibilities of a Beam committer. [1]
>>
>> Thank you Ritesh! And we are looking to see more of your contributions!
>>
>> Kenn, on behalf of the Apache Beam PMC
>>
>> [1]
>>
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>
>

Re: [ANNOUNCE] New committer: Ritesh Ghorse

[Sachin Agarwal via dev]

Congrats Ritesh!

On Thu, Nov 3, 2022 at 4:16 PM Kenneth Knowles  wrote:

> Hi all,
>
> Please join me and the rest of the Beam PMC in welcoming a new committer:
> Ritesh Ghorse (riteshgho...@apache.org)
>
> Ritesh started contributing to Beam in mid-2021 and has contributed
> immensely to bringin the Go SDK to fruition, in addition to contributions
> to Java and Python and release validation.
>
> Considering their contributions to the project over this timeframe, the
> Beam PMC trusts Ritesh with the responsibilities of a Beam committer. [1]
>
> Thank you Ritesh! And we are looking to see more of your contributions!
>
> Kenn, on behalf of the Apache Beam PMC
>
> [1]
>
> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>

[ANNOUNCE] New committer: Ritesh Ghorse

[Kenneth Knowles]

Hi all,

Please join me and the rest of the Beam PMC in welcoming a new committer:
Ritesh Ghorse (riteshgho...@apache.org)

Ritesh started contributing to Beam in mid-2021 and has contributed
immensely to bringin the Go SDK to fruition, in addition to contributions
to Java and Python and release validation.

Considering their contributions to the project over this timeframe, the
Beam PMC trusts Ritesh with the responsibilities of a Beam committer. [1]

Thank you Ritesh! And we are looking to see more of your contributions!

Kenn, on behalf of the Apache Beam PMC

[1]
https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer

[Question][Dataflow][Java][pubsub] Streaming Pipeline Stall Scenarios

[Evan Galpin]

Hi folks,

Hoping to get some definitive answers with respect to streaming pipeline
bundle retry semantics on Dataflow.  I understand that a bundle containing
a "poison pill" (bad data, let's say it causes a null pointer exception
when processing in DoFn) will be retried indefinitely.  What I'm not clear
on are the implications of those retries.


   1. Is it the case that a worker will continuously retry the same "poison
   pill" bundle, and not be able to work on any other/new bundles indefinitely
   after receiving the first poison pill? I've noticed that a small number
   poison pills can cause all processing to stall, even if the bad data
   represents only a very small percentage of the overall data being processed
   2. Is there any implication with windowing and this retry/stall
   scenario?  I've noticed that the scenario where all processing stalls
   entirely is more common for a pipeline where all data is globally
   windowed.  I don't, however, have a solid understanding of how to explain
   that observation; I'd really appreciate any insights that can aid in
   understanding

Thanks,
Evan

Re: Support existing IOs with Schema Transforms

[Chamikara Jayalath via dev]

Thanks for writing this. Added some comments. We should also consider
documenting Schema-Aware Transform API and SchemaTransform authoring
process in the Beam programming guide.

- Cham

On Thu, Nov 3, 2022 at 12:56 PM Ritesh Ghorse via dev 
wrote:

> Thanks for writing this! Having schema transform supported IOs would ease
> up writing multi-language wrappers in Go SDK.
>
> On Thu, Nov 3, 2022 at 2:36 PM Sachin Agarwal via dev 
> wrote:
>
>> I think this is a great idea - making any many existing IOs as possible
>> available to developers in any language is a huge win (and helps reduce the
>> need to re-implement IOs on a language-by-language basis going forward).
>>
>> On Thu, Nov 3, 2022 at 11:25 AM Ahmed Abualsaud via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Hi all,
>>>
>>> There has been an effort to add SchemaTransform capabilities to our
>>> connectors to facilitate the use of multi-lang pipelines. I've drafted a
>>> document below that provides guidelines and examples of how to support IOs
>>> with SchemaTransforms. Please take a look and share your thoughts and
>>> suggestions!
>>>
>>>  Supporting existing connectors with SchemaTrans...
>>> 
>>>
>>>
>>> Best,
>>> Ahmed
>>>
>>

Re: Support existing IOs with Schema Transforms

[Ritesh Ghorse via dev]

Thanks for writing this! Having schema transform supported IOs would ease
up writing multi-language wrappers in Go SDK.

On Thu, Nov 3, 2022 at 2:36 PM Sachin Agarwal via dev 
wrote:

> I think this is a great idea - making any many existing IOs as possible
> available to developers in any language is a huge win (and helps reduce the
> need to re-implement IOs on a language-by-language basis going forward).
>
> On Thu, Nov 3, 2022 at 11:25 AM Ahmed Abualsaud via dev <
> dev@beam.apache.org> wrote:
>
>> Hi all,
>>
>> There has been an effort to add SchemaTransform capabilities to our
>> connectors to facilitate the use of multi-lang pipelines. I've drafted a
>> document below that provides guidelines and examples of how to support IOs
>> with SchemaTransforms. Please take a look and share your thoughts and
>> suggestions!
>>
>>  Supporting existing connectors with SchemaTrans...
>> 
>>
>>
>> Best,
>> Ahmed
>>
>

Re: Support existing IOs with Schema Transforms

[Sachin Agarwal via dev]

I think this is a great idea - making any many existing IOs as possible
available to developers in any language is a huge win (and helps reduce the
need to re-implement IOs on a language-by-language basis going forward).

On Thu, Nov 3, 2022 at 11:25 AM Ahmed Abualsaud via dev 
wrote:

> Hi all,
>
> There has been an effort to add SchemaTransform capabilities to our
> connectors to facilitate the use of multi-lang pipelines. I've drafted a
> document below that provides guidelines and examples of how to support IOs
> with SchemaTransforms. Please take a look and share your thoughts and
> suggestions!
>
>  Supporting existing connectors with SchemaTrans...
> 
>
>
> Best,
> Ahmed
>

Support existing IOs with Schema Transforms

[Ahmed Abualsaud via dev]

Hi all,

There has been an effort to add SchemaTransform capabilities to our
connectors to facilitate the use of multi-lang pipelines. I've drafted a
document below that provides guidelines and examples of how to support IOs
with SchemaTransforms. Please take a look and share your thoughts and
suggestions!

 Supporting existing connectors with SchemaTrans...



Best,
Ahmed

Beam Dependency Check Report (2022-11-03)

[Apache Jenkins Server]

<<< text/html; charset=UTF-8: Unrecognized >>>

Beam High Priority Issue Report (57)

[beamactions]

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/23944  beam_PreCommit_Python_Cron 
regularily failing - test_pardo_large_input flaky
https://github.com/apache/beam/issues/23940 beam_PostCommit_Py_ValCont failing
https://github.com/apache/beam/issues/23815 [Bug]: Neo4j tests failing
https://github.com/apache/beam/issues/23745 [Bug]: Samza 
AsyncDoFnRunnerTest.testSimplePipeline is flaky
https://github.com/apache/beam/issues/23709 [Flake]: Spark batch flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElement and 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle
https://github.com/apache/beam/issues/22969 Discrepancy in behavior of 
`DoFn.process()` when `yield` is combined with `return` statement, or vice versa
https://github.com/apache/beam/issues/22913 [Bug]: 
beam_PostCommit_Java_ValidatesRunner_Flink is flakes in 
org.apache.beam.sdk.transforms.GroupByKeyTest$BasicTests.testAfterProcessingTimeContinuationTriggerUsingState
https://github.com/apache/beam/issues/22321 
PortableRunnerTestWithExternalEnv.test_pardo_large_input is regularly failing 
on jenkins
https://github.com/apache/beam/issues/21713 404s in BigQueryIO don't get output 
to Failed Inserts PCollection
https://github.com/apache/beam/issues/21561 
ExternalPythonTransformTest.trivialPythonTransform flaky
https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: 
Connection refused
https://github.com/apache/beam/issues/21462 Flake in 
org.apache.beam.sdk.io.mqtt.MqttIOTest.testReadObject: Address already in use
https://github.com/apache/beam/issues/21261 
org.apache.beam.runners.dataflow.worker.fn.logging.BeamFnLoggingServiceTest.testMultipleClientsFailingIsHandledGracefullyByServer
 is flaky
https://github.com/apache/beam/issues/21260 Python DirectRunner does not emit 
data at GC time
https://github.com/apache/beam/issues/21123 Multiple jobs running on Flink 
session cluster reuse the persistent Python environment.
https://github.com/apache/beam/issues/21113 
testTwoTimersSettingEachOtherWithCreateAsInputBounded flaky
https://github.com/apache/beam/issues/20976 
apache_beam.runners.portability.flink_runner_test.FlinkRunnerTestOptimized.test_flink_metrics
 is flaky
https://github.com/apache/beam/issues/20975 
org.apache.beam.runners.flink.ReadSourcePortableTest.testExecution[streaming: 
false] is flaky
https://github.com/apache/beam/issues/20974 Python GHA PreCommits flake with 
grpc.FutureTimeoutError on SDK harness startup
https://github.com/apache/beam/issues/20689 Kafka commitOffsetsInFinalize OOM 
on Flink
https://github.com/apache/beam/issues/20108 Python direct runner doesn't emit 
empty pane when it should
https://github.com/apache/beam/issues/19814 Flink streaming flakes in 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundleStateful and 
ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElementStateful
https://github.com/apache/beam/issues/19734 
WatchTest.testMultiplePollsWithManyResults flake: Outputs must be in timestamp 
order (sickbayed)
https://github.com/apache/beam/issues/19241 Python Dataflow integration tests 
should export the pipeline Job ID and console output to Jenkins Test Result 
section


P1 Issues with no update in the last week:

https://github.com/apache/beam/issues/23855 [FLAKY-WORKFLOW] [10535797]: THIS 
IS A TEST, PLEASE IGNORE #1
https://github.com/apache/beam/issues/23627 [Bug]: Website precommit flaky
https://github.com/apache/beam/issues/23525 [Bug]: Default PubsubMessage coder 
will drop message id and orderingKey
https://github.com/apache/beam/issues/23489 [Bug]: add DebeziumIO to the 
connectors page
https://github.com/apache/beam/issues/23306 [Bug]: BigQueryBatchFileLoads in 
python loses data when using WRITE_TRUNCATE
https://github.com/apache/beam/issues/23286 [Bug]: 
beam_PerformanceTests_InfluxDbIO_IT Flaky > 50 % Fail 
https://github.com/apache/beam/issues/22891 [Bug]: 
beam_PostCommit_XVR_PythonUsingJavaDataflow is flaky
https://github.com/apache/beam/issues/22605 [Bug]: Beam Python failure for 
dataflow_exercise_metrics_pipeline_test.ExerciseMetricsPipelineTest.test_metrics_it
https://github.com/apache/beam/issues/22299 [Bug]: JDBCIO Write freeze at 
getConnection() in WriteFn
https://github.com/apache/beam/issues/22115 [Bug]: 
apache_beam.runners.portability.portable_runner_test.PortableRunnerTestWithSubprocesses
 is flaky
https://github.com/apache/beam/issues/22011 [Bug]: 
org.apache.beam.sdk.io.aws2.kinesis.KinesisIOWriteTest.testWriteFailure flaky
https://github.com/apache/beam/issues/21893 [Bug]: BigQuery Storage Write API 
implementation does not support table partitioning
https://github.com/apache/beam/issues/21714 
PulsarIOTest.testReadFromSimpleTopic is very flaky