date:20230109

Re: [VOTE] Release 2.44.0, release candidate #1

2023-01-09 Thread Kenneth Knowles

I have discovered that many pom files are missing from the nexus
repository. I should be able to re-publish a new one. It will take some
time as this is one of the longest-running processes.

On Mon, Jan 9, 2023 at 1:42 PM Kenneth Knowles  wrote:

> Correction: this is release candidate #1.
>
> On Mon, Jan 9, 2023 at 1:25 PM Kenneth Knowles  wrote:
>
>> Hi everyone,
>>
>> Please review and vote on the release candidate #3 for the version
>> 2.44.0, as follows:
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>>
>> Reviewers are encouraged to test their own use cases with the release
>> candidate, and vote +1 if
>> no issues are found.
>>
>> The complete staging area is available for your review, which includes:
>> * GitHub Release notes [1],
>> * the official Apache source release to be deployed to dist.apache.org
>> [2], which is signed with the key with fingerprint 6ED551A8AE02461C [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "v2.44.0-RC1" [5],
>> * website pull request listing the release [6], the blog post [6], and
>> publishing the API reference manual [7].
>> * Java artifacts were built with Gradle 7.5.1 and OpenJDK 1.8.0_232.
>> * Python artifacts are deployed along with the source release to the
>> dist.apache.org [2] and PyPI [8].
>> * Go artifacts and documentation are available at pkg.go.dev [9]
>> (waiting on these to appear)
>> * Validation sheet with a tab for 2.44.0 release to help with validation
>> [10].
>> * Docker images published to Docker Hub [11].
>>
>> The vote will be open for at least 72 hours. It is adopted by majority
>> approval, with at least 3 PMC affirmative votes.
>>
>> For guidelines on how to try the release in your projects, check out our
>> blog post at /blog/validate-beam-release/.
>>
>> Thanks,
>> Kenn
>>
>> [1] https://github.com/apache/beam/milestone/7
>> [2] https://dist.apache.org/repos/dist/dev/beam/2.44.0/
>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>> [4]
>> https://repository.apache.org/content/repositories/orgapachebeam-1289/
>> [5] https://github.com/apache/beam/tree/v2.44.0-RC1
>> [6] https://github.com/apache/beam/pull/24951
>> [7] https://github.com/apache/beam-site/pull/638
>> [8] https://pypi.org/project/apache-beam/2.44.0rc1/
>> [9]
>> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.44.0-RC1/go/pkg/beam
>> [10]
>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=622267910
>> [11] https://hub.docker.com/search?q=apache%2Fbeam=image
>>
>

Re: [VOTE] Release 2.44.0, release candidate #1

2023-01-09 Thread Kenneth Knowles

Correction: this is release candidate #1.

On Mon, Jan 9, 2023 at 1:25 PM Kenneth Knowles  wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #3 for the version 2.44.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> Reviewers are encouraged to test their own use cases with the release
> candidate, and vote +1 if
> no issues are found.
>
> The complete staging area is available for your review, which includes:
> * GitHub Release notes [1],
> * the official Apache source release to be deployed to dist.apache.org
> [2], which is signed with the key with fingerprint 6ED551A8AE02461C [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "v2.44.0-RC1" [5],
> * website pull request listing the release [6], the blog post [6], and
> publishing the API reference manual [7].
> * Java artifacts were built with Gradle 7.5.1 and OpenJDK 1.8.0_232.
> * Python artifacts are deployed along with the source release to the
> dist.apache.org [2] and PyPI [8].
> * Go artifacts and documentation are available at pkg.go.dev [9] (waiting
> on these to appear)
> * Validation sheet with a tab for 2.44.0 release to help with validation
> [10].
> * Docker images published to Docker Hub [11].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> For guidelines on how to try the release in your projects, check out our
> blog post at /blog/validate-beam-release/.
>
> Thanks,
> Kenn
>
> [1] https://github.com/apache/beam/milestone/7
> [2] https://dist.apache.org/repos/dist/dev/beam/2.44.0/
> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> [4] https://repository.apache.org/content/repositories/orgapachebeam-1289/
> [5] https://github.com/apache/beam/tree/v2.44.0-RC1
> [6] https://github.com/apache/beam/pull/24951
> [7] https://github.com/apache/beam-site/pull/638
> [8] https://pypi.org/project/apache-beam/2.44.0rc1/
> [9]
> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.44.0-RC1/go/pkg/beam
> [10]
> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=622267910
> [11] https://hub.docker.com/search?q=apache%2Fbeam=image
>

[VOTE] Release 2.44.0, release candidate #1

2023-01-09 Thread Kenneth Knowles

Hi everyone,

Please review and vote on the release candidate #3 for the version 2.44.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

Reviewers are encouraged to test their own use cases with the release
candidate, and vote +1 if
no issues are found.

The complete staging area is available for your review, which includes:
* GitHub Release notes [1],
* the official Apache source release to be deployed to dist.apache.org [2],
which is signed with the key with fingerprint 6ED551A8AE02461C [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "v2.44.0-RC1" [5],
* website pull request listing the release [6], the blog post [6], and
publishing the API reference manual [7].
* Java artifacts were built with Gradle 7.5.1 and OpenJDK 1.8.0_232.
* Python artifacts are deployed along with the source release to the
dist.apache.org [2] and PyPI [8].
* Go artifacts and documentation are available at pkg.go.dev [9] (waiting
on these to appear)
* Validation sheet with a tab for 2.44.0 release to help with validation
[10].
* Docker images published to Docker Hub [11].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

For guidelines on how to try the release in your projects, check out our
blog post at /blog/validate-beam-release/.

Thanks,
Kenn

[1] https://github.com/apache/beam/milestone/7
[2] https://dist.apache.org/repos/dist/dev/beam/2.44.0/
[3] https://dist.apache.org/repos/dist/release/beam/KEYS
[4] https://repository.apache.org/content/repositories/orgapachebeam-1289/
[5] https://github.com/apache/beam/tree/v2.44.0-RC1
[6] https://github.com/apache/beam/pull/24951
[7] https://github.com/apache/beam-site/pull/638
[8] https://pypi.org/project/apache-beam/2.44.0rc1/
[9]
https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.44.0-RC1/go/pkg/beam
[10]
https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit#gid=622267910
[11] https://hub.docker.com/search?q=apache%2Fbeam=image

[GitHub] [beam-site] kennknowles opened a new pull request, #638: [DO NOT MERGE] Update beam-site for release 2.44.0.

2023-01-09 Thread GitBox



kennknowles opened a new pull request, #638:
URL: https://github.com/apache/beam-site/pull/638

   Content generated from commit b5faa338f8582acf0877902d20a0d0c91ee3cee0.
   
   Apache Beam website sources have been moved to the
   apache/beam repository at: https://github.com/apache/beam/blob/master/website
   Please open pull requests for website contributions there.
   
   This repository hosts generated HTML release documentation (Javadocs, pydocs)
   on the release-docs branch: 
https://github.com/apache/beam-site/tree/release-docs
   branch. Please see the Apache Beam Release guide for details on how to 
publish
   documentation for a new release: 
https://beam.apache.org/contribute/release-guide
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@beam.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

How to write an IO guide draft

2023-01-09 Thread John Casey via dev

Hi All,

I spent the last few weeks of December drafting a "How to write an IO
guide":
https://docs.google.com/document/d/1-WxZTNu9RrLhh5O7Dl5PbnKqz3e5gm1x3gDBBhszVF8/edit#

and an associated code sample: https://github.com/apache/beam/pull/24799

My goal is to make it easier for a new IO developer to create a new IO from
scratch. This is intended to complement the various standards documents
that have been floating around. Where those are intended to
prescribe structure of an IO, this is more focused on the mechanics of
internal design.

Please take a look and let me know what you think,

John

Re: Beam Website Feedback

2023-01-09 Thread Sachin Agarwal via dev

These are great. Thank you so much!

On Mon, Jan 9, 2023 at 6:33 AM Alexey Romanenko 
wrote:

> Always happy to help!
>
> Many thanks for your work to make Beam website better!
>
> —
> Alexey
>
> On 6 Jan 2023, at 21:54, Alex Kosolapov 
> wrote:
>
> Thank you, Ahmet! Happy to help! Both changes [1] and [2] have been
> reviewed and merged by Alexey Romanenko.
>
> We wanted to thank Alexey Romanenko, David Huntsperger, Pablo Estrada,
> Alya Boiko for reviewing and helping to contribute 52 enhancements, fixes
> and case study related additions for the Beam website in the last 6 months
> since July’22! [3]
>
> [1] https://github.com/apache/beam/pull/1
> [2] https://github.com/apache/beam/pull/24747
> [3]
> https://github.com/apache/beam/pulls?page=1=is%3Apr+author%3Abullet03+is%3Aclosed+merged%3A%3E%3D2022-07-01
>
> *From: *Ahmet Altay 
> *Date: *Tuesday, January 3, 2023 at 2:22 PM
> *To: *Alex Kosolapov 
> *Cc: *"dev@beam.apache.org" , Rebecca Szper <
> rsz...@google.com>, Bulat Safiullin , Alexey
> Romanenko , Rajkumar Gupta <
> rajkumargu...@google.com>
> *Subject: *[EXTERNAL] Re: Beam Website Feedback
>
> Thank you Alex and Bulat for improving this. We all very much appreciate
> it.
>
> On Thu, Dec 22, 2022 at 9:21 AM Alex Kosolapov 
> wrote:
>
> Hi all,
>
> We were preparing some improvements for check-links.sh script that is used
> for testing Apache Beam website links during the website build with Bulat (
> @bullet03 ).
>
> We saw several categories of link checks and error statuses:
>
>- 404 - actual incorrect links - fixed in [1] and [2]
>- Valid links that appear to the script as incorrect, e..g., 9xx
>status code for LinkedIn requiring authentication in LinkedIn, some GitHub
>documentation links, example links, some Meetup links, etc.
>
>
> We propose to add a “verified_list” to check_links.sh so that manually
> verified links can be skipped in testing. Current verified list includes 15
> links based on review of most recent test review. Inconvenience of this
> approach is that a verified link may become outdated, and would require an
> update of the “verified_list” in check_links.sh. This approach implemented
> in [3].
>
> [3] also contains check-links.sh improvements:
>
>- Added a function that checks and reports Apache Beam staging website
>links to prevent the production website from having links to staging
>- Added script checks and reports Apache Beam website absolute links
>(links of the form https://beam.apache.org/path) - relative links in
>the sources are preferred to properly build and review website staging
>- Added sorting any invalid links by their error code - this may be
>more convenient for reviewing output
>
>
> [4] - optionally, update absolute links to relative links so that a
> staging website more closely resembles the production website
>
> We submitted [3] and [4] for PR review and tagged Alexey Romanenko to
> kindly help with reviewing these PRs. Please share your comments about
> proposed approach in the PRs or list.
>
> [1] https://github.com/apache/beam/pull/24635
> [2] https://github.com/apache/beam/pull/24744
> [3] https://github.com/apache/beam/pull/1
> [4] https://github.com/apache/beam/pull/24747
>
> Thank you,
> Alex
>
> *From: *Rebecca Szper via dev 
> *Reply-To: *"dev@beam.apache.org" , Rebecca Szper <
> rsz...@google.com>
> *Date: *Wednesday, December 21, 2022 at 10:15 AM
> *To: *Ahmet Altay 
> *Cc: *Alexey Romanenko , dev <
> dev@beam.apache.org>, Rajkumar Gupta 
> *Subject: *[EXTERNAL] Re: Beam Website Feedback
>
> Our team doesn't maintain the Beam website infrastructure, but last time
> something like this came up, David said that there are consultants that
> work on this type of thing. He pinged @bullet03
>  on the Beam ticket, who was able to help.
>
> On Tue, Dec 20, 2022 at 5:06 PM Ahmet Altay  wrote:
>
>
>
> On Tue, Dec 20, 2022 at 1:12 PM Ahmet Altay  wrote:
>
>
>
> On Tue, Dec 20, 2022 at 9:14 AM Alexey Romanenko 
> wrote:
>
> Thanks Ahmet! I’d prefer to fix the links as you did and add the redirect
> from old one - perhaps, there are other similar links that have been
> changed in the same way.
>
>
> Thank you for the review. I fixed it, and added a redirect too.
>
>
>
> Btw, I’m not sure that we still check the broken links as it was before,
> iirc, but probably it would be a good idea to add such check before
> publishing a website.
>
>
> I agree. I also do not know about the state of this. It would be good to
> add that links checker again.
>
>
> Adding @Rebecca Szper  - in case this is something she
> can fix or would know who could fix it.
>
>
>
>
>
> —
> Alexey
>
>
>
>
>
> On 20 Dec 2022, at 18:04, Ahmet Altay via dev  wrote:
>
> I did a search and found a few places with the broken link. Correct links
> should be:
> https://beam.apache.org/get-started/resources/videos-and-podcasts/
>
> I created a PR to update the website (
>

Re: Beam Website Feedback

2023-01-09 Thread Alexey Romanenko

Always happy to help!

Many thanks for your work to make Beam website better!

—
Alexey

> On 6 Jan 2023, at 21:54, Alex Kosolapov  wrote:
> 
> Thank you, Ahmet! Happy to help! Both changes [1] and [2] have been reviewed 
> and merged by Alexey Romanenko.
>  
> We wanted to thank Alexey Romanenko, David Huntsperger, Pablo Estrada, Alya 
> Boiko for reviewing and helping to contribute 52 enhancements, fixes and case 
> study related additions for the Beam website in the last 6 months since 
> July’22! [3]
>  
> [1] https://github.com/apache/beam/pull/1
> [2] https://github.com/apache/beam/pull/24747 
> [3] 
> https://github.com/apache/beam/pulls?page=1=is%3Apr+author%3Abullet03+is%3Aclosed+merged%3A%3E%3D2022-07-01
>  
> From: Ahmet Altay 
> Date: Tuesday, January 3, 2023 at 2:22 PM
> To: Alex Kosolapov 
> Cc: "dev@beam.apache.org" , Rebecca Szper 
> , Bulat Safiullin , Alexey 
> Romanenko , Rajkumar Gupta 
> 
> Subject: [EXTERNAL] Re: Beam Website Feedback
>  
> Thank you Alex and Bulat for improving this. We all very much appreciate it.
>  
> On Thu, Dec 22, 2022 at 9:21 AM Alex Kosolapov  > wrote:
>> Hi all,
>>  
>> We were preparing some improvements for check-links.sh script that is used 
>> for testing Apache Beam website links during the website build with Bulat 
>> (@bullet03 ).
>>  
>> We saw several categories of link checks and error statuses:
>> 404 - actual incorrect links - fixed in [1] and [2]
>> Valid links that appear to the script as incorrect, e..g., 9xx status code 
>> for LinkedIn requiring authentication in LinkedIn, some GitHub documentation 
>> links, example links, some Meetup links, etc.
>>  
>> We propose to add a “verified_list” to check_links.sh so that manually 
>> verified links can be skipped in testing. Current verified list includes 15 
>> links based on review of most recent test review. Inconvenience of this 
>> approach is that a verified link may become outdated, and would require an 
>> update of the “verified_list” in check_links.sh. This approach implemented 
>> in [3].
>>  
>> [3] also contains check-links.sh improvements:
>> Added a function that checks and reports Apache Beam staging website links 
>> to prevent the production website from having links to staging
>> Added script checks and reports Apache Beam website absolute links (links of 
>> the form https://beam.apache.org/path) - relative links in the sources are 
>> preferred to properly build and review website staging
>> Added sorting any invalid links by their error code - this may be more 
>> convenient for reviewing output
>>  
>> [4] - optionally, update absolute links to relative links so that a staging 
>> website more closely resembles the production website
>>  
>> We submitted [3] and [4] for PR review and tagged Alexey Romanenko to kindly 
>> help with reviewing these PRs. Please share your comments about proposed 
>> approach in the PRs or list.
>>  
>> [1] https://github.com/apache/beam/pull/24635
>> [2] https://github.com/apache/beam/pull/24744 
>> [3] https://github.com/apache/beam/pull/1 
>> [4] https://github.com/apache/beam/pull/24747 
>>  
>> Thank you,
>> Alex
>>  
>> From: Rebecca Szper via dev > >
>> Reply-To: "dev@beam.apache.org " 
>> mailto:dev@beam.apache.org>>, Rebecca Szper 
>> mailto:rsz...@google.com>>
>> Date: Wednesday, December 21, 2022 at 10:15 AM
>> To: Ahmet Altay mailto:al...@google.com>>
>> Cc: Alexey Romanenko > >, dev > >, Rajkumar Gupta > >
>> Subject: [EXTERNAL] Re: Beam Website Feedback
>>  
>> Our team doesn't maintain the Beam website infrastructure, but last time 
>> something like this came up, David said that there are consultants that work 
>> on this type of thing. He pinged @bullet03  on 
>> the Beam ticket, who was able to help.
>>  
>> On Tue, Dec 20, 2022 at 5:06 PM Ahmet Altay > > wrote:
>>>  
>>>  
>>> On Tue, Dec 20, 2022 at 1:12 PM Ahmet Altay >> > wrote:
  
  
 On Tue, Dec 20, 2022 at 9:14 AM Alexey Romanenko >>> > wrote:
> Thanks Ahmet! I’d prefer to fix the links as you did and add the redirect 
> from old one - perhaps, there are other similar links that have been 
> changed in the same way.
  
 Thank you for the review. I fixed it, and added a redirect too.
  
>  
> Btw, I’m not sure that we still check the broken links as it was before, 
> iirc, but probably it would be a good idea to add such check before 
> publishing a website.
  
 I agree. I also do not know about the state of this. It would be good to 
 add that links checker again.
>>>  
>>> Adding @Rebecca Szper  - in case this is 
>>> something she can fix or would

Beam High Priority Issue Report (42)

2023-01-09 Thread 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/24934 [Failing Test]: Python PostCommit 
failing: Dataflow test 
apache_beam.io.gcp.bigquery_json_it_test.BigQueryJsonIT.test_query_read 
https://github.com/apache/beam/issues/24776 [Bug]: Race condition in Python SDK 
Harness ProcessBundleProgress
https://github.com/apache/beam/issues/24655 [Bug]: Pipeline fusion should break 
at @RequiresStableInput boundary
https://github.com/apache/beam/issues/24389 [Failing Test]: 
HadoopFormatIOElasticTest.classMethod ExceptionInInitializerError 
ContainerFetchException
https://github.com/apache/beam/issues/24367 [Bug]: workflow.tar.gz cannot be 
passed to flink runner
https://github.com/apache/beam/issues/24313 [Flaky]: 
apache_beam/runners/portability/portable_runner_test.py::PortableRunnerTestWithSubprocesses::test_pardo_state_with_custom_key_coder
https://github.com/apache/beam/issues/24267 [Failing Test]: Timeout waiting to 
lock gradle
https://github.com/apache/beam/issues/23944  beam_PreCommit_Python_Cron 
regularily failing - test_pardo_large_input 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/22961 [Bug]: WriteToBigQuery silently 
skips most of records without job fail
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/21713 404s in BigQueryIO don't get output 
to Failed Inserts PCollection
https://github.com/apache/beam/issues/21695 DataflowPipelineResult does not 
raise exception for unsuccessful states.
https://github.com/apache/beam/issues/21643 FnRunnerTest with non-trivial 
(order 1000 elements) numpy input flakes in non-cython environment
https://github.com/apache/beam/issues/21469 beam_PostCommit_XVR_Flink flaky: 
Connection refused
https://github.com/apache/beam/issues/21262 Python AfterAny, AfterAll do not 
follow spec
https://github.com/apache/beam/issues/21260 Python DirectRunner does not emit 
data at GC time
https://github.com/apache/beam/issues/21121 
apache_beam.examples.streaming_wordcount_it_test.StreamingWordCountIT.test_streaming_wordcount_it
 flakey
https://github.com/apache/beam/issues/21104 Flaky: 
apache_beam.runners.portability.fn_api_runner.fn_runner_test.FnApiRunnerTestWithGrpcAndMultiWorkers
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/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/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/24464 [Epic]: Implement 
FileWriteSchemaTransformProvider
https://github.com/apache/beam/issues/23875 [Bug]: beam.Row.__eq__ returns true 
for unequal rows
https://github.com/apache/beam/issues/23525 [Bug]: Default PubsubMessage coder 
will drop message id and orderingKey
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/22115 [Bug]: 
apache_beam.runners.portability.portable_runner_test.PortableRunnerTestWithSubprocesses
 is flaky
https://github.com/apache/beam/issues/21714 
PulsarIOTest.testReadFromSimpleTopic is very flaky
https://github.com/apache/beam/issues/21708 beam_PostCommit_Java_DataflowV2, 
testBigQueryStorageWrite30MProto failing consistently
https://github.com/apache/beam/issues/21706 Flaky timeout in github Python unit 
test action 
StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer
https://github.com/apache/beam/issues/21700 
--dataflowServiceOptions=use_runner_v2 is broken

Re: [VOTE] Release 2.44.0, release candidate #1

Re: [VOTE] Release 2.44.0, release candidate #1

[VOTE] Release 2.44.0, release candidate #1

[GitHub] [beam-site] kennknowles opened a new pull request, #638: [DO NOT MERGE] Update beam-site for release 2.44.0.

How to write an IO guide draft

Re: Beam Website Feedback

Re: Beam Website Feedback

Beam High Priority Issue Report (42)

8 matches

Site Navigation

Mail list logo

Footer information