Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira]

I just sent out an update on the RC3 vote thread, and in it I mentioned
some issues I had with the Python RC validation Jenkins target
. It
seemed appropriate to shunt that rant list of grievances over here instead
of cluttering up the vote thread, since I've been using this thread more
for general progress updates.

Frankly, that Jenkins target is really unwieldy for RC validation. It took
me like 2 days to finally get a useful signal from it for a variety of
reasons, the big one being that the target takes over 4 hours to run from
end to end, and the quickstarts and mobile gaming examples are interspersed
with each other, despite the validation sheet separating them. So if I get
a failure and I try a fix, it takes an extremely long time to actually get
a signal on it. Plus, the whole thing runs sequentially, so if one test
fails, none of the subsequent tests run at all, which makes debugging even
more of a pain.

Finally, the mobile examples are all used with a persistent BQ table on
apache-beam-testing instead of creating and deleting temporary tables. This
means that the examples are used with already populated tables, which
messes with test results (we can't tell if the example failed to write to
the table since it's already populated), and it means that
apache-beam-testing has constantly growing BQ tables hogging up space.

I worked around those issues for this release, but I think this target is a
good candidate to be refactored for future release managers (along with a
bunch of other little pain points I've been writing down). It shouldn't be
too hard to split it into two Jenkins targets, one for the quickstarts and
one for the mobile game examples, to adjust it so that processing continues
even if there's one failure, and to adjust it so that it generates
temporary BQ tables and deletes them once it's done.

I think I can figure those changes out myself, but if anyone has expertise
working with these tests and can find the time to help out (or make
the changes yourself), I would really appreciate it. While I can manage it,
it would probably get done faster and with better quality by someone who's
already familiar with these tests.

On Mon, Aug 31, 2020 at 10:25 PM Daniel Oliveira 
wrote:

> The first release candidate is out. It took longer than I expected thanks
> to running into a few bits of user-unfriendliness, but mostly bugs due to
> me accidentally using JDK 11 with Gradle instead of JDK 8. I'm writing that
> down (along with all the other little difficulties I ran into) to make
> improvements to the release guide for the next release manager.
>
> Anyway, I sent out a thread for voting on the RC, so any issues with it
> can be mentioned in that thread. I just wanted to use this one as a
> progress report on my release experience, in case anyone is wondering what
> caused the release candidate to take so long.
>
> On Wed, Aug 12, 2020 at 6:09 PM Daniel Oliveira 
> wrote:
>
>> Release branch has been cut
>> . Reminder: Don't
>> commit to the release branch directly. If you have a fix for a
>> release-blocking issue, contact me to include it as a cherry pick.
>>
>> Next steps in the process are for me to verify the release branch and to
>> triage release-blocking bugs
>> . I've
>> already begun going through bugs and have been leaving comments, so if you
>> have any release-blocking bugs on Jira, please check them.
>>
>> If you have an existing bug that you believe is release-blocking, check
>> it against the requirements in the Beam release guide
>> 
>>  first,
>> and if you believe a cherry-pick would be accepted then mark the Jira with
>> "2.24.0" as the fix version and send me the PR that will need to be
>> cherry-picked.
>>
>> On Tue, Aug 11, 2020 at 6:59 PM Daniel Oliveira 
>> wrote:
>>
>>> I'd like to send out a last minute reminder to fill out CHANGES.md
>>>  with any major
>>> changes that are going to be in 2.24.0. If you need a quick review for
>>> that, just add me as a reviewer to your PR (GitHub username is "youngoli").
>>> I'll keep an eye out for those until around 5 PM.
>>>
>>> On another note, I need some help with setup from the release guide
>>> 
>>> :
>>> 1. I need someone to add me as a maintainer of the apache-beam package
>>> on PyPI. Username: danoliveira
>>> 2. Someone might need to create a new version in JIRA
>>> .
>>> I'm not sure about this one because 2.25.0 already exists, I don't know if
>>> 2.26.0 needs to be created or if that's for the next release.
>>>
>>> On Mon, Aug 10, 2020 

Re: [VOTE] Release 2.24.0, release candidate #3

[Daniel Oliveira]

Hey everyone,

I finally got a decent enough signal from the Python release validations
running on Jenkins
 to
finish up the validation I signed up for. I have some grievances with that
target, but I'll shunt that off to another thread and keep the vote thread
uncluttered.

Looking at the validation sheet

it seems that we've tested the majority of targets, with the exception of
some Flink/Spark tests and Nexmark tests. We also already have 3
binding +1s on this thread. So *I'm planning on closing the vote tomorrow*,
leaving at least 24 hours from this email for any last minute testing,
objections, or finishing discussions. If anyone has any concerns and wants
me to hold off on the release for a bit longer, this is the time to mention
them.

Thanks,
Daniel Oliveira

On Thu, Sep 10, 2020 at 4:59 PM Thomas Weise  wrote:

> +1 (binding)
>
> Rebased fork and run internal performance tests.
>
> While doing so, I run into the unit test issue below with the fn_runner
> (Python direct runner), which did not occur with 2.21 [1]. That processing
> time timers are not supported wasn't an issue previously, because the
> timer, though declared, wasn't exercised in the unit test.
>
> Is there a plan/JIRA to support processing time timers with the direct
> runner?
>
> Thanks,
> Thomas
>
>
> [1]
> https://gist.github.com/tweise/6f8ca6341711f579b0ed9943b8f25138#file-synthetic_stateful-py-L250
>
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/pipeline.py:555: in 
> __exit__
> self.result = self.run()
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/pipeline.py:521: in 
> run
> allow_proto_holders=True).run(False)
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/pipeline.py:534: in 
> run
> return self.runner.run_pipeline(self, self._options)
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/runners/direct/direct_runner.py:119:
>  in run_pipeline
> return runner.run_pipeline(pipeline, options)
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py:176:
>  in run_pipeline
> pipeline.to_runner_api(default_environment=self._default_environment))
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py:182:
>  in run_via_runner_api
> self._check_requirements(pipeline_proto)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _
>
> self =  object at 0x7fd2a896b400>
> pipeline_proto = components {
>   transforms {
> key: "ref_AppliedPTransform_AppliedPTransform_1"
> value {
>   subtransforms: "ref...}
> }
> root_transform_ids: "ref_AppliedPTransform_AppliedPTransform_1"
> requirements: "beam:requirement:pardo:stateful:v1"
>
>
> def _check_requirements(self, pipeline_proto):
>   """Check that this runner can satisfy all pipeline requirements."""
>   supported_requirements = set(self.supported_requirements())
>   for requirement in pipeline_proto.requirements:
> if requirement not in supported_requirements:
>   raise ValueError(
>   'Unable to run pipeline with requirement: %s' % requirement)
>   for transform in pipeline_proto.components.transforms.values():
> if transform.spec.urn == common_urns.primitives.TEST_STREAM.urn:
>   raise NotImplementedError(transform.spec.urn)
> elif transform.spec.urn in translations.PAR_DO_URNS:
>   payload = proto_utils.parse_Bytes(
>   transform.spec.payload, beam_runner_api_pb2.ParDoPayload)
>   for timer in payload.timer_family_specs.values():
> if timer.time_domain != beam_runner_api_pb2.TimeDomain.EVENT_TIME:
> > raise NotImplementedError(timer.time_domain)
> E NotImplementedError: 2
>
> /code/venvs/venv/lib/python3.6/site-packages/apache_beam/runners/portability/fn_api_runner/fn_runner.py:283:
>  NotImplementedError
>
>
>
> On Thu, Sep 10, 2020 at 4:41 PM Robert Bradshaw 
> wrote:
>
>> Given the additional information, I am upgrading my vote to +1 (binding)
>> based on my prior analysis.
>>
>> On Thu, Sep 10, 2020 at 4:14 PM Kyle Weaver  wrote:
>>
>>> +1 (non-binding)
>>>
>>> Validated wordcount with Python 3.7.8 and Flink 1.10.0 (both loopback
>>> and using the Docker image). Also Python 3.7.8 loopback with an embedded
>>> Spark cluster.
>>>
>>> On Thu, Sep 10, 2020 at 2:32 PM Daniel Oliveira 
>>> wrote:
>>>
 By the way, most of the validation so far has covered Direct runner and
 Dataflow, but Flink and Spark still have little validation, so if anyone
 can help with those it will help speed up the release.

 On Thu, Sep 10, 2020 at 2:12 PM Daniel Oliveira 
 wrote:

> So I tracked the --temp_location issue down to
> 

Re: I would like to assign a BEAM ticke to myself

[Luke Cwik]

Welcome to the community. I have added you as a contributor and assigned
BEAM-10875 to you.

On Mon, Sep 14, 2020 at 4:16 PM terry xian  wrote:

> Hi,
>
> I have created a jira ticket: [BEAM-10875] Support NUMERIC type in
> spanner schema parser - ASF JIRA
> , and would like to
> assign it to myself (already had a PR)
>
> [BEAM-10875] Support NUMERIC type in spanner schema parser - ASF JIRA
>
> 
>
> The jira ticket was in "Tirage Needed" for several days. What should I do?
> Should I get a contributor role to assign the ticket to myself?
>
> Thanks!
>
>
>

I would like to assign a BEAM ticke to myself

[terry xian]

Hi,
I have created a jira ticket: [BEAM-10875] Support NUMERIC type in spanner 
schema parser - ASF JIRA, and would like to assign it to myself (already had a 
PR)

| 
| 
|  | 
[BEAM-10875] Support NUMERIC type in spanner schema parser - ASF JIRA


 |

 |

 |


The jira ticket was in "Tirage Needed" for several days. What should I do? 
Should I get a contributor role to assign the ticket to myself?
Thanks!

Re: contributor permission for Beam Jira tickets

[Kenneth Knowles]

Hi Michael,

I've added you to the "Contributors" role so you should be able to take
those Jira tickets now. Thank you for the report & fix!

Kenn

On Mon, Sep 14, 2020 at 3:41 PM Michael Ballou 
wrote:

> Just following up.  I created 2 issues in Apache Beam related to the new
> ReadFromBigQuery class.  I have fixes for the 2 issues I created and would
> like to be given access to assign the Jira ticket to myself and submit a PR
> for both fixes.
> BEAM-10792
> BEAM-10811
>
> Can someone let me know what I need to do?   I'm looking at
> https://beam.apache.org/contribute/ for reference and it says to email
> this group.
>
> Thanks,
> Mike Ballou
>
> On Fri, Aug 21, 2020 at 6:21 PM Michael Ballou 
> wrote:
>
>> This is Michael Ballou from Lumiata.  I'm working with Apache Beam and
>> Google Dataflow and would like to submit a fix for an issue I found.
>> Can someone add me as a contributor for Beam's Jira issue tracker so I
>> can assign the ticket to myself?
>> I created ticket BEAM-10792
>>  already.
>>
>> I have a fix ready to submit as well.  Do I request github permission to
>> create the branch and PR here?
>>
>> Jira username: mballou
>>
>> Thanks!
>>
>> --
>> *Michael Ballou, Senior Staff Engineer*
>> michael.bal...@lumiata.com
>> Lumiata.com  | Twitter 
>>  | LinkedIn 
>>
>> This email message, including any attachments, is for the sole use of the
>> intended recipient(s) and may contain confidential or proprietary
>> information. Any unauthorized review, use, disclosure or distribution is
>> prohibited. If you are not the intended recipient, immediately contact the
>> sender by reply e-mail and destroy all copies of the original message.
>>
>
>
> --
> *Michael Ballou, Senior Staff Engineer*
> michael.bal...@lumiata.com | 949-633-6430 <(949)%20633-6430>
> Lumiata.com  | Twitter 
>  | LinkedIn 
>
> This email message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential or proprietary
> information. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, immediately contact the
> sender by reply e-mail and destroy all copies of the original message.
>

Re: contributor permission for Beam Jira tickets

[Michael Ballou]

Just following up.  I created 2 issues in Apache Beam related to the new
ReadFromBigQuery class.  I have fixes for the 2 issues I created and would
like to be given access to assign the Jira ticket to myself and submit a PR
for both fixes.
BEAM-10792
BEAM-10811

Can someone let me know what I need to do?   I'm looking at
https://beam.apache.org/contribute/ for reference and it says to email this
group.

Thanks,
Mike Ballou

On Fri, Aug 21, 2020 at 6:21 PM Michael Ballou 
wrote:

> This is Michael Ballou from Lumiata.  I'm working with Apache Beam and
> Google Dataflow and would like to submit a fix for an issue I found.
> Can someone add me as a contributor for Beam's Jira issue tracker so I can
> assign the ticket to myself?
> I created ticket BEAM-10792
>  already.
>
> I have a fix ready to submit as well.  Do I request github permission to
> create the branch and PR here?
>
> Jira username: mballou
>
> Thanks!
>
> --
> *Michael Ballou, Senior Staff Engineer*
> michael.bal...@lumiata.com
> Lumiata.com  | Twitter 
>  | LinkedIn 
>
> This email message, including any attachments, is for the sole use of the
> intended recipient(s) and may contain confidential or proprietary
> information. Any unauthorized review, use, disclosure or distribution is
> prohibited. If you are not the intended recipient, immediately contact the
> sender by reply e-mail and destroy all copies of the original message.
>


-- 
*Michael Ballou, Senior Staff Engineer*
michael.bal...@lumiata.com | 949-633-6430
Lumiata.com  | Twitter  |
LinkedIn 

This email message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential or proprietary
information. Any unauthorized review, use, disclosure or distribution is
prohibited. If you are not the intended recipient, immediately contact the
sender by reply e-mail and destroy all copies of the original message.

Re: Infra Improvements

[Kenneth Knowles]

I think the big bucket makes sense and is pretty self-documenting. I think
we'll hit some name conflicts between our infra component and ASF INFRA.
They just took the best name :-)

I think "testing" is a worse name, really. It is documented as "Testing:
General Infrastructure" but someone not reading that could put all sorts of
things in the "testing" component.

Since you can tag as many components as you want, I think having a bunch of
fine-grained components could be fine. On the other hand, I don't want to
invent a component for "email report about our dependencies".

I'm happy to create an "infra" component but is there a synonym, or a small
collection of other terms, we could use?

Kenn

On Fri, Sep 11, 2020 at 3:39 PM Tyson Hamilton  wrote:

>
>
> On Fri, Sep 11, 2020 at 3:29 PM Kyle Weaver  wrote:
>
>> > Could someone create an ‘infra’ component in Jira (I don’t have access)?
>>
>>
>> Could these issues go under the "testing" component?
>>
>
> That is an option. There are things beyond testing as well like Github
> Actions, Jenkins inventory jobs, email reports, artifact publishing, etc.
> so IMO having a general 'infra' would be handy. Another option is to have
> dedicated components for each of these things but the proliferation may
> become a problem.
>
>
>>
>> On Fri, Sep 11, 2020 at 3:11 PM Tyson Hamilton 
>> wrote:
>>
>>> Hi All,
>>>
>>> Below is a summary of the improvements made to Beam’s infrastructure in
>>> the last few months. The completion of this work is thanks to Damian
>>> (damgad) and Tobiasz (TobKed)  from Polidea. Thank you!!!
>>>
>>>
>>>-
>>>
>>>Jenkins tests are not always triggered / Switch to new jenkins infra
>>>-
>>>
>>>   Beam now has a dedicated Jenkins master.
>>>   -
>>>
>>>   Beam now has 4x the Jenkins agents which essentially eliminated
>>>   build queues.
>>>   -
>>>
>>>Jenkins /tmp directory periodic cleanup
>>>-
>>>
>>>   Moved to the inventory job for better transparency [tmp-cleanup].
>>>   -
>>>
>>>Jenkins post commit tests does not clearly point to failing tests
>>>-
>>>
>>>   installed Test Result History Plugin [test-results-plugin,
>>>   screenshot] to start measuring flakiness. This plugin produces a 
>>> similar
>>>   matrix of test results as the Grafana Chart but it is clickable and 
>>> has
>>>   aggregation.
>>>   -
>>>
>>>BEAM-3105 Cancel Jenkins builds when an update to a PR makes a prior
>>>build irrelevant
>>>-
>>>
>>>BEAM-3105 Cancel Jenkins builds when an update to a PR makes a prior
>>>build irrelevant
>>>-
>>>
>>>BEAM-9388 Github Actions instead of Travis CI as a build framework
>>>(Wheel Files)
>>>-
>>>
>>>BEAM-9271 Fix "beam_PostCommit_Py_ValCont failure due to timeout"
>>>-
>>>
>>>BEAM-4709 Javadoc build only tested during release
>>>-
>>>
>>>BEAM-8665 Run 2 (one for Java, one for Python) new test suites in
>>>Windows environment.
>>>-
>>>
>>>BEAM-10281 Jenkins Load Sharing Improvements (stackdriver agents &
>>>extend nb of executors)
>>>-
>>>
>>>BEAM-10542 Investigate a possible Nexmark performance regression
>>>around 06/16
>>>-
>>>
>>>INFRA-20649 Beam Jenkins not triggering jobs from phrases
>>>-
>>>
>>>BEAM-10831 Fix broken Beam Dependency Check Report
>>>-
>>>
>>>BEAM-10837 Remove unused beam_PerformanceTests_Analysis Jenkins Job
>>>-
>>>
>>>BEAM-10835 Improve Github Actions cancelling duplicated runs
>>>-
>>>
>>>BEAM-10807 Performance test weekly email sent to dev@ list
>>>automatically [perf-email]
>>>-
>>>
>>>Apply more strict credentials bindings to Jenkins jobs
>>>-
>>>
>>>Configure seed & dependency check jobs to be triggered only by
>>>committers
>>>
>>>
>>> There are plans to continue to invest into Beam’s infra in the future. A
>>> few examples include,
>>>
>>>-
>>>
>>>Test Flakiness tracking improvements (e.g. increase build history
>>>retention)
>>>-
>>>
>>>Reduce flakiness with cross-job caching (maven, pypi, gradle, build
>>>cache, licenses, …)
>>>-
>>>
>>>More Github Actions (java artifacts, docker images, flaky test
>>>quarantine like Apache Ariflow)
>>>
>>>
>>> If you have additional infra related tasks, or pain points, please
>>> create a Jira issue so we can track them. Contributions are always welcome.
>>> Could someone create an ‘infra’ component in Jira (I don’t have access)?
>>>
>>>
>>> -Tyson
>>>
>>> [tmp-cleanup]:
>>> https://github.com/apache/beam/commit/50366bae1c86136331be097f0f0250bd619dc7f8
>>>
>>> [test-results-plugin]: https://plugins.jenkins.io/test-results-analyzer/
>>>
>>> [test-results-screenshot]: https://photos.app.goo.gl/E4cGpp5WqxYhwtTAA
>>>
>>> [perf-email]:
>>> https://lists.apache.org/thread.html/rc0054933a3e40c35f09641786a873391988caf6529899ec8bba67772%40%3Cdev.beam.apache.org%3E
>>>
>>>

Re: [DISCUSS] Deprecation of AWS SDK v2 IO connectors

[Kenneth Knowles]

I just checked the stats viewable at
https://repository.apache.org/#central-stat if you have a login. It looks
like v1 is between 10x and 100x more downloads. Basically it seems like
almost noone is using v2. Do users know about the v2 module? Or did I read
the stats wrong?

Kenn

On Fri, Sep 11, 2020 at 12:15 PM Alexey Romanenko 
wrote:

> Yes, sure. Though, I’d prefer to keep only v2 ones after a while (several
> releases) in case if there are no users objections.
>
> On 11 Sep 2020, at 19:41, Robert Bradshaw  wrote:
>
> Makes sense to me. We could keep the v1 ones around as-is with fairly low
> cost, right?
>
> On Fri, Sep 11, 2020 at 10:13 AM Alexey Romanenko <
> aromanenko@gmail.com> wrote:
>
>> Hello,
>>
>> In Beam, there are two versions of AWS IO connectors for Java SDK - based
>> on AWS SDK v1 [1] and v2 [2]. For now, they are pretty equal in terms of
>> functionality, but since AWS SDK v2 is more modern (it's a major rewrite of
>> the version 1.x code base, it’s built on top of Java 8+ and adds more
>> features [3]), then it would be more logical to use only V2. Also, it’s not
>> reasonable to support two versions of similar connectors, since it’s a big
>> pain for us, and it will be more clear for users which package of AWS
>> connectors to use .
>>
>> According to this, I’d propose to deprecate all Java AWS IO connectors V1
>> (+ KinesisIO which is in a different package for now) starting from Beam
>> 2.25 and then add new features only to V2 connectors. Bug fixes should be
>> applied to V2 connectors in the first order, and to V1 connectors if it’s
>> only necessary.
>>
>> What are the community thoughts on this? Any pros and cons that I'm
>> missing?
>>
>>
>> [1]
>> https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services
>> [2]
>> https://github.com/apache/beam/tree/master/sdks/java/io/amazon-web-services2
>> [3]
>> https://docs.aws.amazon.com/sdk-for-java/v2/developer-guide/welcome.html
>>
>>
>>
>

Beam Dependency Check Report (2020-09-14)

[Apache Jenkins Server]

High Priority Dependency Updates Of Beam Python SDK:


  Dependency Name
  Current Version
  Latest Version
  Release Date Of the Current Used Version
  Release Date Of The Latest Release
  JIRA Issue
  
cachetools
3.1.1
4.1.1
2019-12-23
2020-07-08BEAM-9017
chromedriver-binary
83.0.4103.39.0
86.0.4240.22.0
2020-07-08
2020-09-07BEAM-10426
fastavro
0.23.6
1.0.0.post1
2020-08-03
2020-08-28BEAM-10798
mock
2.0.0
3.0.5
2019-05-20
2019-05-20BEAM-7369
mypy-protobuf
1.18
1.23
2020-03-24
2020-06-29BEAM-10346
oauth2client
3.0.0
4.1.3
2018-12-10
2018-12-10BEAM-6089
pyarrow
0.17.1
1.0.1
2020-07-27
2020-08-24BEAM-10582
PyHamcrest
1.10.1
2.0.2
2020-01-20
2020-07-08BEAM-9155
pytest
4.6.11
6.0.2
2020-07-08
2020-09-14BEAM-8606
pytest-xdist
1.34.0
2.1.0
2020-08-17
2020-08-28BEAM-10713
setuptools
49.6.0
50.3.0
2020-08-17
2020-09-07BEAM-10714
tenacity
5.1.5
6.2.0
2019-11-11
2020-06-29BEAM-8607
High Priority Dependency Updates Of Beam Java SDK:


  Dependency Name
  Current Version
  Latest Version
  Release Date Of the Current Used Version
  Release Date Of The Latest Release
  JIRA Issue
  
com.amazonaws:amazon-kinesis-producer
0.13.1
0.14.1
2019-07-31
2020-07-31BEAM-10628
com.azure:azure-storage-blob
12.1.0
12.8.0
2019-12-05
2020-08-13BEAM-10800
com.datastax.cassandra:cassandra-driver-core
3.8.0
4.0.0
2019-10-29
2019-03-18BEAM-8674
com.esotericsoftware:kryo
4.0.2
5.0.0-RC9
2018-03-20
2020-08-14BEAM-5809
com.esotericsoftware.kryo:kryo
2.21
2.24.0
2013-02-27
2014-05-04BEAM-5574
com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin
0.29.0
0.33.0
2020-07-20
2020-09-14BEAM-6645
com.google.api.grpc:grpc-google-cloud-pubsub-v1
1.85.1
1.90.1
2020-03-09
2020-08-04BEAM-8677
com.google.api.grpc:grpc-google-common-protos
1.12.0
1.18.1
2018-06-29
2020-08-11BEAM-8633
com.google.api.grpc:proto-google-cloud-bigquerystorage-v1beta1
0.85.1
0.105.1
2020-01-08
2020-08-31BEAM-8678
com.google.api.grpc:proto-google-cloud-bigtable-v2
1.9.1
1.15.0
2020-01-10
2020-09-02BEAM-8679
com.google.api.grpc:proto-google-cloud-pubsub-v1
1.85.1
1.90.1
2020-03-09
2020-08-04BEAM-8681
com.google.apis:google-api-services-bigquery
v2-rev20200719-1.30.10
v2-rev20200827-1.30.10
2020-07-26
2020-09-03BEAM-8684
com.google.apis:google-api-services-clouddebugger
v2-rev20200501-1.30.10
v2-rev20200807-1.30.10
2020-07-14
2020-08-17BEAM-8750
com.google.apis:google-api-services-cloudresourcemanager
v1-rev20200720-1.30.10
v2-rev20200831-1.30.10
2020-07-25
2020-09-03BEAM-8751
com.google.apis:google-api-services-dataflow
v1b3-rev20200713-1.30.10
v1beta3-rev12-1.20.0
2020-07-25
2015-04-29BEAM-8752
com.google.apis:google-api-services-healthcare
v1beta1-rev20200713-1.30.10
v1-rev20200901-1.30.10
2020-07-24
2020-09-09BEAM-10349
com.google.apis:google-api-services-pubsub
v1-rev20200713-1.30.10
v1-rev20200807-1.30.10
2020-07-25
2020-08-14BEAM-8753
com.google.apis:google-api-services-storage
v1-rev20200611-1.30.10
v1-rev20200814-1.30.10
2020-07-10
2020-09-07BEAM-8754
com.google.auto.service:auto-service
1.0-rc6
1.0-rc7
2019-07-16
2020-05-13BEAM-5541
com.google.auto.service:auto-service-annotations
1.0-rc6
1.0-rc7
2019-07-16
2020-05-13BEAM-10350
com.google.cloud:google-cloud-bigquery
1.108.0
1.117.1
2020-02-28
2020-08-31BEAM-8687
com.google.cloud:google-cloud-bigquerystorage
0.125.0-beta
1.5.1
2020-02-20
2020-08-31BEAM-8755
com.google.cloud:google-cloud-datacatalog
0.32.1
1.0.1
2020-02-04
2020-08-11BEAM-10351
com.google.cloud:google-cloud-dlp
1.1.4
2.1.0
2020-05-04
2020-08-11BEAM-10352

Re: [ANNOUNCE] New committer: Reza Ardeshir Rokni

[Katarzyna Kucharczyk]

Congratulations Reza! :)

On Mon, Sep 14, 2020 at 10:05 AM Alexey Romanenko 
wrote:

> Congratulations! Thanks Reza for your contributions!
>
> On 12 Sep 2020, at 10:00, Jan Lukavský  wrote:
>
> Congrats Reza!
> On 9/12/20 5:29 AM, Thomas Weise wrote:
>
> Congratulations!
>
>
> On Fri, Sep 11, 2020, 5:54 PM Andrew Psaltis 
> wrote:
>
>> Congrats!
>>
>> On Sat, Sep 12, 2020 at 7:43 AM Reza Rokni  wrote:
>>
>>> Thanx everyone! Looking forward to being able to contribute more :-)
>>>
>>> On Sat, Sep 12, 2020 at 4:33 AM Valentyn Tymofieiev 
>>> wrote:
>>>
 Congrats!

 On Thu, Sep 10, 2020 at 8:08 PM Connell O'Callaghan <
 conne...@google.com> wrote:

> Excellent- well done Reza!!!
>
> On Thu, Sep 10, 2020 at 7:35 PM Austin Bennett <
> whatwouldausti...@gmail.com> wrote:
>
>> Thanks and congrats, Reza!
>>
>> On Thu, Sep 10, 2020 at 5:48 PM Heejong Lee 
>> wrote:
>>
>>> Congratulations!
>>>
>>> On Thu, Sep 10, 2020 at 4:42 PM Robert Bradshaw 
>>> wrote:
>>>
 Thank you and welcome, Reza!

 On Thu, Sep 10, 2020 at 4:00 PM Ahmet Altay 
 wrote:

> Congratulations Reza! And thank you for your contributions!
>
> On Thu, Sep 10, 2020 at 3:59 PM Chamikara Jayalath <
> chamik...@google.com> wrote:
>
>> Congrats Reza!
>>
>> On Thu, Sep 10, 2020 at 10:35 AM Kenneth Knowles 
>> wrote:
>>
>>> Hi all,
>>>
>>> Please join me and the rest of the Beam PMC in welcoming a new
>>> committer: Reza Ardeshir Rokni.
>>>
>>> Reza has been part of the Beam community since 2017! Reza has
>>> spearheaded advanced Beam examples [1], blogged and presented at 
>>> multiple
>>> Beam Summits. Reza helps out users on the mailing lists [2] and
>>> StackOverflow [3]. When Reza's work uncovers a missing feature in 
>>> Beam, he
>>> adds it [4]. Considering these contributions, the Beam PMC trusts 
>>> Reza with
>>> the responsibilities of a Beam committer [5].
>>>
>>> Thank you, Reza, for your contributions.
>>>
>>> Kenn
>>>
>>> [1] https://github.com/apache/beam/pull/3961
>>> [2]
>>> https://lists.apache.org/list.html?u...@beam.apache.org:gte=0d:reza%20rokni
>>> [3] https://stackoverflow.com/tags/apache-beam/topusers
>>> [4] https://github.com/apache/beam/pull/11929
>>> [5]
>>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>>
>>>
>>>
>>
>>
>
>


>>>
>>>
>>
>> --
> Your feedback welcomed for Connello!!!
> 
>

>

Re: [ANNOUNCE] New committer: Reza Ardeshir Rokni

[Alexey Romanenko]

Congratulations! Thanks Reza for your contributions!

> On 12 Sep 2020, at 10:00, Jan Lukavský  wrote:
> 
> Congrats Reza!
> On 9/12/20 5:29 AM, Thomas Weise wrote:
>> Congratulations!
>> 
>> 
>> On Fri, Sep 11, 2020, 5:54 PM Andrew Psaltis > > wrote:
>> Congrats!
>> 
>> On Sat, Sep 12, 2020 at 7:43 AM Reza Rokni > > wrote:
>> Thanx everyone! Looking forward to being able to contribute more :-)
>> 
>> On Sat, Sep 12, 2020 at 4:33 AM Valentyn Tymofieiev > > wrote:
>> Congrats!
>> 
>> On Thu, Sep 10, 2020 at 8:08 PM Connell O'Callaghan > > wrote:
>> Excellent- well done Reza!!!
>> 
>> On Thu, Sep 10, 2020 at 7:35 PM Austin Bennett > > wrote:
>> Thanks and congrats, Reza!  
>> 
>> On Thu, Sep 10, 2020 at 5:48 PM Heejong Lee > > wrote:
>> Congratulations!
>> 
>> On Thu, Sep 10, 2020 at 4:42 PM Robert Bradshaw > > wrote:
>> Thank you and welcome, Reza!
>> 
>> On Thu, Sep 10, 2020 at 4:00 PM Ahmet Altay > > wrote:
>> Congratulations Reza! And thank you for your contributions!
>> 
>> On Thu, Sep 10, 2020 at 3:59 PM Chamikara Jayalath > > wrote:
>> Congrats Reza!
>> 
>> On Thu, Sep 10, 2020 at 10:35 AM Kenneth Knowles > > wrote:
>> Hi all,
>> 
>> Please join me and the rest of the Beam PMC in welcoming a new committer: 
>> Reza Ardeshir Rokni.
>> 
>> Reza has been part of the Beam community since 2017! Reza has spearheaded 
>> advanced Beam examples [1], blogged and presented at multiple Beam Summits. 
>> Reza helps out users on the mailing lists [2] and StackOverflow [3]. When 
>> Reza's work uncovers a missing feature in Beam, he adds it [4]. Considering 
>> these contributions, the Beam PMC trusts Reza with the responsibilities of a 
>> Beam committer [5].
>> 
>> Thank you, Reza, for your contributions.
>> 
>> Kenn
>> 
>> [1] https://github.com/apache/beam/pull/3961 
>> 
>> [2] 
>> https://lists.apache.org/list.html?u...@beam.apache.org:gte=0d:reza%20rokni 
>> 
>> [3] https://stackoverflow.com/tags/apache-beam/topusers 
>> 
>> [4] https://github.com/apache/beam/pull/11929 
>> [5] 
>> https://beam.apache.org/contribute/become-a-committer/#an-apache-beam-committer
>>  
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> Your feedback welcomed for Connello!!! 
>>