Web APIs I/O Connector Guide

2024-03-08 Thread Damon Douglas
Hello Everyone,

The Beam website now has a published guide on a new transform that supports
reads and writes with Web APIs such as REST or gRPC.

https://beam.apache.org/documentation/io/built-in/webapis/

Best,

Damon


Re: Issue building python SDK with M2 Mac

2024-03-08 Thread Valentyn Tymofieiev via dev
it sounds like the the error might be happening during building of python
wheels, it seems that `-arch ` parameter is not being correctly evaluated
for your platform and is omitted. I am not sure what is causing this.
I am also not sure what dependency generates that command line
(distutils/setuptools), perhaps updating it would help. or maybe you could
try to do it in a docker container.

On Fri, Mar 8, 2024 at 10:38 AM XQ Hu via dev  wrote:

> I do not have the problem to do this on my M1 by cloning the repo and
> using conda to create venv with python 3.11 and installing it with pip
> install -e ".[gcp,test]". It installs numpy with 1.26.4.
>
> On Thu, Mar 7, 2024 at 7:48 AM Joey Tran 
> wrote:
>
>> Hey all,
>>
>> I'm trying to get a beam python SDK dev environment going but I'm a bit
>> stuck. I'm just settings things up with a virtual env as specified in the
>> docs[1], but `pip install -e .[gcp,test]` ends with a clang error:
>>
>> ```
>>   clang -Wsign-compare -Wunreachable-code -fno-common -dynamic
>> -DNDEBUG -g -fwrapv -O3 -Wall -isysroot
>> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch
>> -I/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/numpy/core/include
>> -I/Users/jtran/repo/hjtran/beam/sdks/python/env/include
>> -I/opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/include/python3.11
>> -c apache_beam/coders/coder_impl_row_encoders.c -o
>> /var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/tmpro15g_f6.build-temp/apache_beam/coders/coder_impl_row_encoders.o
>>   clang: error: invalid arch name '-arch
>> -I/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/numpy/core/include'
>>   Traceback (most recent call last):
>> File
>> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/unixccompiler.py",
>> line 185, in _compile
>>   self.spawn(compiler_so + cc_args + [src, '-o', obj] +
>> extra_postargs)
>> File
>> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/ccompiler.py",
>> line 1041, in spawn
>>   spawn(cmd, dry_run=self.dry_run, **kwargs)
>> File
>> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/spawn.py",
>> line 70, in spawn
>>   raise DistutilsExecError(
>>   distutils.errors.DistutilsExecError: command '/usr/bin/clang'
>> failed with exit code 1
>>
>>   During handling of the above exception, another exception occurred:
>>
>> ```
>>
>> I'm pretty stumped as to how to go forward.
>>
>> [1]
>> https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-VirtualEnvironmentSetup
>>
>


Re: Issue building python SDK with M2 Mac

2024-03-08 Thread XQ Hu via dev
I do not have the problem to do this on my M1 by cloning the repo and using
conda to create venv with python 3.11 and installing it with pip install -e
".[gcp,test]". It installs numpy with 1.26.4.

On Thu, Mar 7, 2024 at 7:48 AM Joey Tran  wrote:

> Hey all,
>
> I'm trying to get a beam python SDK dev environment going but I'm a bit
> stuck. I'm just settings things up with a virtual env as specified in the
> docs[1], but `pip install -e .[gcp,test]` ends with a clang error:
>
> ```
>   clang -Wsign-compare -Wunreachable-code -fno-common -dynamic
> -DNDEBUG -g -fwrapv -O3 -Wall -isysroot
> /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk -arch
> -I/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/numpy/core/include
> -I/Users/jtran/repo/hjtran/beam/sdks/python/env/include
> -I/opt/homebrew/opt/python@3.11/Frameworks/Python.framework/Versions/3.11/include/python3.11
> -c apache_beam/coders/coder_impl_row_encoders.c -o
> /var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/tmpro15g_f6.build-temp/apache_beam/coders/coder_impl_row_encoders.o
>   clang: error: invalid arch name '-arch
> -I/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/numpy/core/include'
>   Traceback (most recent call last):
> File
> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/unixccompiler.py",
> line 185, in _compile
>   self.spawn(compiler_so + cc_args + [src, '-o', obj] +
> extra_postargs)
> File
> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/ccompiler.py",
> line 1041, in spawn
>   spawn(cmd, dry_run=self.dry_run, **kwargs)
> File
> "/private/var/folders/n1/6qk3ljm97h32j1g7qg5s0prhgq/T/pip-build-env-0q14luhy/overlay/lib/python3.11/site-packages/setuptools/_distutils/spawn.py",
> line 70, in spawn
>   raise DistutilsExecError(
>   distutils.errors.DistutilsExecError: command '/usr/bin/clang' failed
> with exit code 1
>
>   During handling of the above exception, another exception occurred:
>
> ```
>
> I'm pretty stumped as to how to go forward.
>
> [1]
> https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-VirtualEnvironmentSetup
>


Re: [EXTERNAL] Re: Hiding logging for beam playground examples

2024-03-08 Thread Vlado Djerek via dev
Hi Joey,

We just deployed the 2.54 changes on playground. Can you now check?

Thanks,
Vlado


From: Joey Tran 
Sent: Friday, March 8, 2024 2:45:32 PM
To: Andrey Devyatkin
Subject: [EXTERNAL] Re: Hiding logging for beam playground examples

Ah thanks Andrey! I had assumed that since my change was in a release that went 
out a few weeks ago that Playground would've been redeployed by now. I'll check 
playground again in an hour or two to see if my changes did anything :)

On Fri, Mar 8, 2024 at 8:28 AM Andrey Devyatkin 
mailto:andrey.devyat...@akvelon.com>> wrote:
Hi Joey,

Thanks for reaching out! I see that your changes haven't been deploed yet, so 
I've triggered the corresponding job and Playground will be updated soon.

Thanks,
Andrey

From: Joey Tran mailto:joey.t...@schrodinger.com>>
Reply to: "dev@beam.apache.org" 
mailto:dev@beam.apache.org>>
Date: Thursday, 7 March 2024 at 22:33
To: Valentyn Tymofieiev mailto:valen...@google.com>>
Subject: [EXTERNAL] Re: Hiding logging for beam playground examples

I ended up making this change[1] but it looks like Playground is still 
outputting all the log statements. Could someone help me with this? I suppose 
it's best to try and actually test this, but I had a hard time getting the 
environment set up.

[1]https://github.com/apache/beam/pull/29948


















































































"ghnt

[1] https://github.com/apache/beam/pull/29948#event-11504996254

On Thu, Nov 16, 2023 at 7:42 AM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
Good idea though it ended up being a shallow trace
```
  File 
"/opt/playground/backend/executable_files/91e3e49b-7197-4252-a8bd-93c5b252ed55/91e3e49b-7197-4252-a8bd-93c5b252ed55.py",
 line 57, in 
assert False
```
I think I found where the log level is set anyways
```
https://github.com/apache/beam/blob/master/playground/infrastructure/logger.py#L39
```

When I have some time, I'll try doing a local deployment of playground and 
modifying those log levels

On Wed, Nov 15, 2023 at 10:52 PM Valentyn Tymofieiev 
mailto:valen...@google.com>> wrote:
I am also not familiar with Playground. I suspect you could try to make it 
crash and maybe find a stacktrace? Setting logging could like like so: 
https://github.com/apache/beam/blob/729c4de416b8252ec99f0a1253ac7af3023733df/sdks/python/apache_beam/examples/wordcount.py#L110

On Wed, Nov 15, 2023 at 12:06 PM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
The motivating example does not use LogElements, just Map(print)
https://beam.apache.org/documentation/transforms/python/aggregation/combineglobally/#example-2-combining-with-a-lambda-function

Some examples of the extraneous logging:
```
2023-09-08 22:46:37,334 [INFO]   
2023-09-08 22:46:37,336 [INFO] Creating state cache with size 104857600
2023-09-08 22:46:37,338 [INFO] Created Worker handler 
 for environment 
ref_Environment_default_environment_2 (beam:env:embedded_python:v1, b'')
```

The example code itself doesn't set the log level in some playground code. Does 
anyone have a pointer to where? I'm not familiar

On Wed, Nov 15, 2023 at 2:10 PM Valentyn Tymofieiev via dev 
mailto:dev@beam.apache.org>> wrote:
Are the examples using LogElements? 
https://github.com/apache/beam/blob/2012107a0fa2bb3fedf1b5aedcb49445534b2dad/sdks/python/apache_beam/transforms/util.py#L1271

Note that LogElements by default prints to stdout, but can be configured to use 
a different logger. We could also change the default.

On Tue, Nov 14, 2023 at 9:48 AM Robert Bradshaw via dev 
mailto:dev@beam.apache.org>> wrote:
+1 to at least setting the log level to higher than info. Some runner
logging (e.g. job started/done) may be useful.

On Tue, Nov 14, 2023 at 9:37 AM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
>
> Hi all,
>
> I just had a workshop to demo beam for people at my company and there was a 
> bit of confusion about whether the beam python playground examples were even 
> working and it turned out they just got confused by all the runner logging 
> that is output.
>
> Is this worth keeping? It seems like it'd be a common source of 

Re: Hiding logging for beam playground examples

2024-03-08 Thread Joey Tran
Ah thanks Andrey! I had assumed that since my change was in a release that
went out a few weeks ago that Playground would've been redeployed by now.
I'll check playground again in an hour or two to see if my changes did
anything :)

On Fri, Mar 8, 2024 at 8:28 AM Andrey Devyatkin <
andrey.devyat...@akvelon.com> wrote:

> Hi Joey,
>
> Thanks for reaching out! I see that your changes haven't been deploed yet,
> so I've triggered the corresponding job and Playground will be updated soon.
>
> Thanks,
> Andrey
>
>
>
> *From: *Joey Tran 
> *Reply to: *"dev@beam.apache.org" 
> *Date: *Thursday, 7 March 2024 at 22:33
> *To: *Valentyn Tymofieiev 
> *Subject: *[EXTERNAL] Re: Hiding logging for beam playground examples
>
>
>
> I ended up making this change[1] but it looks like Playground is still
> outputting all the log statements. Could someone help me with this? I
> suppose it's best to try and actually test this, but I had a hard time
> getting the environment set up.
>
> [1]https://github.com/apache/beam/pull/29948
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> "ghnt
>
> [1] https://github.com/apache/beam/pull/29948#event-11504996254
>
>
>
> On Thu, Nov 16, 2023 at 7:42 AM Joey Tran 
> wrote:
>
> Good idea though it ended up being a shallow trace
> ```
>   File
> "/opt/playground/backend/executable_files/91e3e49b-7197-4252-a8bd-93c5b252ed55/91e3e49b-7197-4252-a8bd-93c5b252ed55.py",
> line 57, in 
> assert False
> ```
> I think I found where the log level is set anyways
> ```
>
> https://github.com/apache/beam/blob/master/playground/infrastructure/logger.py#L39
> ```
>
> When I have some time, I'll try doing a local deployment of playground and
> modifying those log levels
>
>
>
> On Wed, Nov 15, 2023 at 10:52 PM Valentyn Tymofieiev 
> wrote:
>
> I am also not familiar with Playground. I suspect you could try to make it
> crash and maybe find a stacktrace? Setting logging could like like so:
> https://github.com/apache/beam/blob/729c4de416b8252ec99f0a1253ac7af3023733df/sdks/python/apache_beam/examples/wordcount.py#L110
>
>
>
> On Wed, Nov 15, 2023 at 12:06 PM Joey Tran 
> wrote:
>
> The motivating example does not use LogElements, just Map(print)
>
> https://beam.apache.org/documentation/transforms/python/aggregation/combineglobally/#example-2-combining-with-a-lambda-function
>
> Some examples of the extraneous logging:
> ```
> 2023-09-08 22:46:37,334 [INFO]   populate_data_channel_coders at 0x7ff2665e1a20> 
> 2023-09-08 22:46:37,336 [INFO] Creating state cache with size 104857600
> 2023-09-08 22:46:37,338 [INFO] Created Worker handler
>  object at 0x7ff2664c9870> for environment
> ref_Environment_default_environment_2 (beam:env:embedded_python:v1, b'')
> ```
>
> The example code itself doesn't set the log level in some playground code.
> Does anyone have a pointer to where? I'm not familiar
>
>
>
> On Wed, Nov 15, 2023 at 2:10 PM Valentyn Tymofieiev via dev <
> dev@beam.apache.org> wrote:
>
> Are the examples using LogElements?
> https://github.com/apache/beam/blob/2012107a0fa2bb3fedf1b5aedcb49445534b2dad/sdks/python/apache_beam/transforms/util.py#L1271
>
>
>
> Note that LogElements by default prints to stdout, but can be configured
> to use a different logger. We could also change the default.
>
>
>
> On Tue, Nov 14, 2023 at 9:48 AM Robert Bradshaw via dev <
> dev@beam.apache.org> wrote:
>
> +1 to at least setting the log level to higher than info. Some runner
> logging (e.g. job started/done) may be useful.
>
> On Tue, Nov 14, 2023 at 9:37 AM Joey Tran 
> wrote:
> >
> > Hi all,
> >
> > I just had a workshop to demo beam for people at my company and there
> was a bit of confusion about whether the beam python playground examples
> were even working and it turned out they just got confused by all the
> runner logging that is output.
> >
> > Is this worth keeping? It seems like it'd be a common source of
> confusion for new users
> >
> > Cheers,
> > Joey
>
>


Re: Hiding logging for beam playground examples

2024-03-08 Thread Andrey Devyatkin via dev
Hi Joey,

Thanks for reaching out! I see that your changes haven't been deploed yet, so 
I've triggered the corresponding job and Playground will be updated soon.

Thanks,
Andrey

From: Joey Tran 
Reply to: "dev@beam.apache.org" 
Date: Thursday, 7 March 2024 at 22:33
To: Valentyn Tymofieiev 
Subject: [EXTERNAL] Re: Hiding logging for beam playground examples

I ended up making this change[1] but it looks like Playground is still 
outputting all the log statements. Could someone help me with this? I suppose 
it's best to try and actually test this, but I had a hard time getting the 
environment set up.

[1]https://github.com/apache/beam/pull/29948


















































































"ghnt

[1] https://github.com/apache/beam/pull/29948#event-11504996254

On Thu, Nov 16, 2023 at 7:42 AM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
Good idea though it ended up being a shallow trace
```
  File 
"/opt/playground/backend/executable_files/91e3e49b-7197-4252-a8bd-93c5b252ed55/91e3e49b-7197-4252-a8bd-93c5b252ed55.py",
 line 57, in 
assert False
```
I think I found where the log level is set anyways
```
https://github.com/apache/beam/blob/master/playground/infrastructure/logger.py#L39
```

When I have some time, I'll try doing a local deployment of playground and 
modifying those log levels

On Wed, Nov 15, 2023 at 10:52 PM Valentyn Tymofieiev 
mailto:valen...@google.com>> wrote:
I am also not familiar with Playground. I suspect you could try to make it 
crash and maybe find a stacktrace? Setting logging could like like so: 
https://github.com/apache/beam/blob/729c4de416b8252ec99f0a1253ac7af3023733df/sdks/python/apache_beam/examples/wordcount.py#L110

On Wed, Nov 15, 2023 at 12:06 PM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
The motivating example does not use LogElements, just Map(print)
https://beam.apache.org/documentation/transforms/python/aggregation/combineglobally/#example-2-combining-with-a-lambda-function

Some examples of the extraneous logging:
```
2023-09-08 22:46:37,334 [INFO]   
2023-09-08 22:46:37,336 [INFO] Creating state cache with size 104857600
2023-09-08 22:46:37,338 [INFO] Created Worker handler 
 for environment 
ref_Environment_default_environment_2 (beam:env:embedded_python:v1, b'')
```

The example code itself doesn't set the log level in some playground code. Does 
anyone have a pointer to where? I'm not familiar

On Wed, Nov 15, 2023 at 2:10 PM Valentyn Tymofieiev via dev 
mailto:dev@beam.apache.org>> wrote:
Are the examples using LogElements? 
https://github.com/apache/beam/blob/2012107a0fa2bb3fedf1b5aedcb49445534b2dad/sdks/python/apache_beam/transforms/util.py#L1271

Note that LogElements by default prints to stdout, but can be configured to use 
a different logger. We could also change the default.

On Tue, Nov 14, 2023 at 9:48 AM Robert Bradshaw via dev 
mailto:dev@beam.apache.org>> wrote:
+1 to at least setting the log level to higher than info. Some runner
logging (e.g. job started/done) may be useful.

On Tue, Nov 14, 2023 at 9:37 AM Joey Tran 
mailto:joey.t...@schrodinger.com>> wrote:
>
> Hi all,
>
> I just had a workshop to demo beam for people at my company and there was a 
> bit of confusion about whether the beam python playground examples were even 
> working and it turned out they just got confused by all the runner logging 
> that is output.
>
> Is this worth keeping? It seems like it'd be a common source of confusion for 
> new users
>
> Cheers,
> Joey


Beam High Priority Issue Report (64)

2024-03-08 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/30530 The LoadTests Java GBK Smoke job is 
flaky
https://github.com/apache/beam/issues/30529 The PostCommit Java Sickbay job is 
flaky
https://github.com/apache/beam/issues/30528 The Dask Runner Tests job is flaky
https://github.com/apache/beam/issues/30527 The PostCommit Java IO Performance 
Tests job is flaky
https://github.com/apache/beam/issues/30526 The PerformanceTests xlang KafkaIO 
Python job is flaky
https://github.com/apache/beam/issues/30525 The PostCommit Python 
ValidatesContainer Dataflow With RC job is flaky
https://github.com/apache/beam/issues/30524 The PerformanceTests SingleStoreIO 
job is flaky
https://github.com/apache/beam/issues/30523 The PostCommit Java SingleStoreIO 
IT job is flaky
https://github.com/apache/beam/issues/30522 The Build and Version Runner Docker 
Image job is flaky
https://github.com/apache/beam/issues/30521 The LoadTests Go Combine Flink 
Batch job is flaky
https://github.com/apache/beam/issues/30520 The LoadTests Python Combine Flink 
Streaming job is flaky
https://github.com/apache/beam/issues/30519 The PostCommit XVR GoUsingJava 
Dataflow job is flaky
https://github.com/apache/beam/issues/30518 The Update Python Depedencies job 
is flaky
https://github.com/apache/beam/issues/30517 The PostCommit XVR Direct job is 
flaky
https://github.com/apache/beam/issues/30516 The PostCommit Java ValidatesRunner 
SparkStructuredStreaming job is flaky
https://github.com/apache/beam/issues/30515 The LoadTests Go SideInput Flink 
Batch job is flaky
https://github.com/apache/beam/issues/30514 The Clean Up Prebuilt SDK Images 
job is flaky
https://github.com/apache/beam/issues/30513 The PostCommit Python job is flaky
https://github.com/apache/beam/issues/30512 The PostCommit Java PVR Spark Batch 
job is flaky
https://github.com/apache/beam/issues/30511 The LoadTests Python Smoke job is 
flaky
https://github.com/apache/beam/issues/30510 The PostCommit Java InfluxDbIO 
Integration Test job is flaky
https://github.com/apache/beam/issues/30508 The PostCommit Java ValidatesRunner 
Flink job is flaky
https://github.com/apache/beam/issues/30507 The LoadTests Go GBK Flink Batch 
job is flaky
https://github.com/apache/beam/issues/30506 The TypeScript Tests job is flaky
https://github.com/apache/beam/issues/30505 The PostRelease Nightly Snapshot 
job is flaky
https://github.com/apache/beam/issues/30504 The LoadTests Python Combine 
Dataflow Streaming job is flaky
https://github.com/apache/beam/issues/30503 The PostCommit Java ValidatesRunner 
Flink Java11 job is flaky
https://github.com/apache/beam/issues/30502 The LoadTests Go CoGBK Flink Batch 
job is flaky
https://github.com/apache/beam/issues/30498 [Bug]: Beam Sql is ignoring aliases 
fields in some situations which causes to huge data loss
https://github.com/apache/beam/issues/30447 [Failing Test]: 
beam_PostRelease_NightlySnapshot red due to various flakes in Dataflow example 
tests
https://github.com/apache/beam/issues/29971 [Bug]: FixedWindows not working for 
large Kafka topic
https://github.com/apache/beam/issues/29926 [Bug]: FileIO: lack of timeouts may 
cause the pipeline to get stuck indefinitely
https://github.com/apache/beam/issues/29902 [Bug]: Messages are not ACK on 
Pubsub starting Beam 2.52.0 on Flink Runner in detached mode
https://github.com/apache/beam/issues/29099 [Bug]: FnAPI Java SDK Harness 
doesn't update user counters in OnTimer callback functions
https://github.com/apache/beam/issues/28760 [Bug]: EFO Kinesis IO reader 
provided by apache beam does not pick the event time for watermarking
https://github.com/apache/beam/issues/28383 [Failing Test]: 
org.apache.beam.runners.dataflow.worker.StreamingDataflowWorkerTest.testMaxThreadMetric
https://github.com/apache/beam/issues/28326 Bug: 
apache_beam.io.gcp.pubsublite.ReadFromPubSubLite not working
https://github.com/apache/beam/issues/27892 [Bug]: ignoreUnknownValues not 
working when using CreateDisposition.CREATE_IF_NEEDED 
https://github.com/apache/beam/issues/27616 [Bug]: Unable to use 
applyRowMutations() in bigquery IO apache beam java
https://github.com/apache/beam/issues/27486 [Bug]: Read from datastore with 
inequality filters
https://github.com/apache/beam/issues/27314 [Failing Test]: 
bigquery.StorageApiSinkCreateIfNeededIT.testCreateManyTables[1]
https://github.com/apache/beam/issues/27238 [Bug]: Window trigger has lag when 
using Kafka and GroupByKey on Dataflow Runner
https://github.com/apache/beam/issues/26911 [Bug]: UNNEST ARRAY with a nested 
ROW (described below)
https://github.com/apache/beam/issues/26343 [Bug]: 
apache_beam.io.gcp.bigquery_read_it_test.ReadAllBQTests.test_read_queries is 
flaky
https://github.com/apache/beam/issues/26329 [Bug]: BigQuerySourceBase does not