Re: Interest to join GSoC - 2020

[Aldair Coronel Ruíz]

Hi Pablo!

I just uploaded my proposal.

Thank you very much.


On Mon, Mar 30, 2020 at 5:33 PM Aldair Coronel Ruíz <
aldai...@ciencias.unam.mx> wrote:

> Hi Pablo!
>
> I am working on the finishing touches. I'll upload it later today.
>
> Thank you for your time!
>
> On Mon, Mar 30, 2020 at 4:16 PM Pablo Estrada  wrote:
>
>> Aldair, can you please prepare your application for submission? I don't
>> see it in the ASF organization's submitted/draft applications.
>>
>> On Mon, Mar 30, 2020 at 1:00 PM Pablo Estrada  wrote:
>>
>>> Thanks Aldair!
>>> Taking a look.
>>>
>>> On Sun, Mar 29, 2020 at 3:42 PM Aldair Coronel Ruíz <
>>> aldai...@ciencias.unam.mx> wrote:
>>>
 Hi, I am Aldair, I am a junior college student studying CS at UNAM in
 Mexico City.
 I am interested in starting to contribute to open source projects, that
 is why I would love to participate in GSoC-2020 by adding support for Azure
 Blobstore file system in Apache Beam Python SDK.

 *Here you can find my proposal. Feel free to add comments.*

 https://docs.google.com/document/d/1iax7Rkxoe3dxsAdxLwc8bkFGM6axom0foOePyjKI-6Y/edit?usp=sharing

 Thank you
 --
 *Aldair Coronel Ruiz*


>
> --
> *Aldair Coronel Ruiz*
>
>

-- 
*Aldair Coronel Ruiz*

Re: [VOTE + INPUT] Beam Mascot Designs, 3rd iteration - Deadline Wednesday, April 1

[Joshua B. Harrison]

On Mon, Mar 30, 2020 at 8:09 PM Julian Bruno  wrote:

> Hello Apache Beam Community,
>
> We need a third input from the community to finish the design. Please
> share your input no later than Wednesday, April 1st, at noon Pacific Time.
> Below you will find a link to the presentation of the work process and we
> are eager to know what you think of the current design [1].
>
> Our question to you:
>
> 1. Do you prefer stripes or no stripes?
>
I prefer the logo with stripes.

>
> Please reply inline, so it is clear what exactly you are referring to. The
> vote and input phase will be open until Wednesday, April 1st, at 12 pm
> Pacific Time. We will incorporate the feedback into the final design
> iteration of the mascot.
>
>
> Please find below the attached source file (.SVG) and a High-Quality Image
> (.PNG).
>
> Thank you,
>
> --
> Julian Bruno // Visual Artist & Graphic Designer
>  (510) 367-0551 / SF Bay Area, CA
> www.instagram.com/julbro.art
>
> [1]
>
>  3/30 - Mascot Weekly Update
> 
>
>
>
> ᐧ
>


-- 
Joshua Harrison |  Software Engineer |  joshharri...@gmail.com
 |  404-433-0242

Re: Interest to join GSoC - 2020

[Aldair Coronel Ruíz]

Hi Pablo!

I am working on the finishing touches. I'll upload it later today.

Thank you for your time!

On Mon, Mar 30, 2020 at 4:16 PM Pablo Estrada  wrote:

> Aldair, can you please prepare your application for submission? I don't
> see it in the ASF organization's submitted/draft applications.
>
> On Mon, Mar 30, 2020 at 1:00 PM Pablo Estrada  wrote:
>
>> Thanks Aldair!
>> Taking a look.
>>
>> On Sun, Mar 29, 2020 at 3:42 PM Aldair Coronel Ruíz <
>> aldai...@ciencias.unam.mx> wrote:
>>
>>> Hi, I am Aldair, I am a junior college student studying CS at UNAM in
>>> Mexico City.
>>> I am interested in starting to contribute to open source projects, that
>>> is why I would love to participate in GSoC-2020 by adding support for Azure
>>> Blobstore file system in Apache Beam Python SDK.
>>>
>>> *Here you can find my proposal. Feel free to add comments.*
>>>
>>> https://docs.google.com/document/d/1iax7Rkxoe3dxsAdxLwc8bkFGM6axom0foOePyjKI-6Y/edit?usp=sharing
>>>
>>> Thank you
>>> --
>>> *Aldair Coronel Ruiz*
>>>
>>>

-- 
*Aldair Coronel Ruiz*

Re: [PROPOSAL] Leveraging SQL TableProviders for Cross-Language IOs

[Robert Bradshaw]

A belated but very enthusiastic +1 to this proposal. Added some
comments to the doc.

On Thu, Jan 16, 2020 at 9:05 AM Kenneth Knowles  wrote:
>
> Nice! This is quite clever.
>
> Kenn
>
> On Mon, Jan 13, 2020 at 5:08 PM Chamikara Jayalath  
> wrote:
>>
>> Thanks Brian. Added some comments.
>>
>> On Mon, Jan 13, 2020 at 2:25 PM Brian Hulette  wrote:
>>>
>>> Hi everyone,
>>> I have a proposal that I think can unify two problem sets:
>>>   1) adding more IOs for Beam SQL, and
>>>   2) making more (Row-based) Java IOs available in Python as cross-language 
>>> transforms
>>>
>>> The basic idea is to create a single cross-language transform that exposes 
>>> all Beam SQL IOs via the TableProvider interface. A design document is 
>>> available here: https://s.apache.org/xlang-table-provider
>>>
>>> Please take a look and let me know what you think. Thanks!
>>> Brian

Re: Google Summer of Coding Proposal

[Rui Wang]

Thanks Qihang! The proposal looks good!


-Rui

On Mon, Mar 30, 2020 at 9:30 AM Qihang Zeng  wrote:

> Dear Beam Community,
>
> Hello! My name is Qihang and I am a candidate for this year's google
> summer of coding. I am a senior in CS major at New York University
> Shanghai. Previously, I had some experience with Apache Parquet, Apache
> Carbondata and Apache Spark. I have long been interested in participating
> in some ASF projects, particularly databases projects.
>
> One of the Beam projects caught my attention and I started to contact
> mentor Mr. Rui Wang about 2 weeks ago. Mr. Wang gave me some advice and I
> finished a proposal which is attached below. Though it is now very close to
> the deadline, do not hesitate to give any comments. : ) I have also shared
> the draft through the google summer of coding portal and anyone could edit
> it or review it.
>
> Sincerely,
> Qihang
>

Re: Interest to join GSoC - 2020

[Pablo Estrada]

Thanks Aldair!
Taking a look.

On Sun, Mar 29, 2020 at 3:42 PM Aldair Coronel Ruíz <
aldai...@ciencias.unam.mx> wrote:

> Hi, I am Aldair, I am a junior college student studying CS at UNAM in
> Mexico City.
> I am interested in starting to contribute to open source projects, that is
> why I would love to participate in GSoC-2020 by adding support for Azure
> Blobstore file system in Apache Beam Python SDK.
>
> *Here you can find my proposal. Feel free to add comments.*
>
> https://docs.google.com/document/d/1iax7Rkxoe3dxsAdxLwc8bkFGM6axom0foOePyjKI-6Y/edit?usp=sharing
>
> Thank you
> --
> *Aldair Coronel Ruiz*
>
>

Implementing type hints on multi-output PTransforms

[Joshua B. Harrison]

Hey all,

I brought up an issue recently on the user forums noting issues around type
hints and multi-output PTransforms:
https://lists.apache.org/thread.html/r94bf2e43f09a290dbe87d5a8d7eedb34ea215e0bea861521cbdb0c1c%40%3Cuser.beam.apache.org%3E

As mentioned there, I think that a NotImplementedError should be raised
when attaching type hints to multi-output PTransforms while the correct
implementation is figured out. And that a 'correct' implementation would
look something like the Union typehints that are expected on multi-input
PTransforms.

I am happy to help out and wanted to get the discussion started around what
the community would like to see here. Thank you all for a great product.

Best,
Joshua

-- 
Joshua Harrison |  Software Engineer |  joshharri...@gmail.com
 |  404-433-0242

Re: [DISCUSS] [PROPOSAL] Redesigning the structure for Beam docs

[Reuven Lax]

This looks overall great! one note: it appears to be missing recent
additions to the documentation (a large section on programming with state &
timers). I'm also soon going to merge.a bunch of changes to document using
Beam with schemas. We need to make sure not to lose this new documentation
when we switch over.

Reuven

On Thu, Mar 26, 2020 at 3:31 PM Rose Nguyen  wrote:

> Hi there,
>
> As part of the documentation revamping process [1] and ongoing website
> migration [2] [3], Aizhamal, David, and I would like to propose this website
> redesign
> 
> [4]. It lists the rationale and proposed layout that we believe, after
> collecting feedback and brainstorming with various Beam users/community
> members, will improve the usability of Beam.
>
> We'd like to share this design plan as we begin to finalize it. If you
> have feedback or comments, we'd like to hear from you!
>
> [1]
> https://docs.google.com/document/d/1HlRHfmc9MvKkFEf2gfIL3RYVxTmBXQL4sXjAGGOjeiI/edit#heading=h.5rqdbnson7px
> [2]
> https://lists.apache.org/thread.html/rfab4cc1411318c3f4667bee051df68f37be11846ada877f3576c41a9%40%3Cdev.beam.apache.org%3E
> [3]
>
> https://lists.apache.org/thread.html/r7fa6d710c0a1959cce5108e460d71c306ce5756cf96af818b41cb7ca%40%3Cdev.beam.apache.org%3E
> [4]
> https://docs.google.com/document/d/1btXMkQGqYaU9pUjYh0iCNrbXf4pAHe3tBFsLQ_cLYHg/edit?usp=sharing
>
> Stay well,
> --
> Rose Thị Nguyễn
>

Re: Jenkins jobs not running for my PR 10438

[Kamil Wasilewski]

Done.

On Mon, Mar 30, 2020 at 4:58 PM Tomo Suzuki  wrote:

> Hi Beam committers,
> (Thanks Ahmet)
>
> Would you retrigger the following 5 jobs for
> https://github.com/apache/beam/pull/11156 ?
> Run Dataflow ValidatesRunner
> Run Java PreCommit
> Run Portable_Python PreCommit
> Run PythonFormatter PreCommit
> Run Website PreCommit
>
>
> On Thu, Mar 26, 2020 at 9:45 PM Ahmet Altay  wrote:
>
>> Done.
>>
>> On Thu, Mar 26, 2020 at 2:37 PM Tomo Suzuki  wrote:
>>
>>> Hi Beam committers,
>>> (Thanks Ahmet for previous attempt)
>>>
>>> Would you trigger
>>> - The failed "Run Java Precommit" for
>>> https://github.com/apache/beam/pull/11208,
>>> - and the precommit checks for https://github.com/apache/beam/pull/11156  
>>> with
>>> the following 6 checks?
>>> Run Java PostCommit
>>> Run Java HadoopFormatIO Performance Test
>>> Run BigQueryIO Streaming Performance Test Java
>>> Run Dataflow ValidatesRunner
>>> Run Spark ValidatesRunner
>>> Run SQL Postcommit
>>>
>>> On Tue, Mar 24, 2020 at 6:37 PM Ahmet Altay  wrote:
>>>
 KInd of done. 11208 is running the tests. 11156 did not start all the
 tests. Someone could retry that again in a bit.

 On Tue, Mar 24, 2020 at 12:11 PM Tomo Suzuki 
 wrote:

> Hi Beam committers,
>
> Would you trigger precommit checks for
> https://github.com/apache/beam/pull/11156 and
> https://github.com/apache/beam/pull/11208 with the following 6 checks?
> Run Java PostCommit
> Run Java HadoopFormatIO Performance Test
> Run BigQueryIO Streaming Performance Test Java
> Run Dataflow ValidatesRunner
> Run Spark ValidatesRunner
> Run SQL Postcommit
>
>
> On Fri, Mar 20, 2020 at 11:13 AM Jan Lukavský  wrote:
>
>> Hi, done.
>> On 3/20/20 3:59 PM, Tomo Suzuki wrote:
>>
>> HI Beam committers,
>> (Thanks Ahmet)
>>
>> Would you re-run the presubmit checks for
>> https://github.com/apache/beam/pull/11168 with the followings?
>> Run Java PostCommit
>> Run Java HadoopFormatIO Performance Test
>> Run BigQueryIO Streaming Performance Test Java
>> Run Dataflow ValidatesRunner
>> Run Spark ValidatesRunner
>> Run SQL Postcommit
>>
>>
>> On Wed, Mar 18, 2020 at 9:09 PM Ahmet Altay  wrote:
>>
>>> Done.
>>>
>>> On Wed, Mar 18, 2020 at 5:57 PM Tomo Suzuki 
>>> wrote:
>>>
 Hi Beam committers,
 (Alexey, thank you!)

 1. Would you run the 2 failed checks Java PreCommit and Python
 PreCommit for https://github.com/apache/beam/pull/11156

 2. Would you run the precommit checks for
 https://github.com/apache/beam/pull/11168 with the following 6
 commands?
 Run Java PostCommit
 Run Java HadoopFormatIO Performance Test
 Run BigQueryIO Streaming Performance Test Java
 Run Dataflow ValidatesRunner
 Run Spark ValidatesRunner
 Run SQL Postcommit





 On Wed, Mar 18, 2020 at 1:08 PM Alexey Romanenko <
 aromanenko@gmail.com> wrote:

> Done
>
> On 18 Mar 2020, at 15:25, Tomo Suzuki  wrote:
>
> Hi Beam committers,
>
> Would you trigger the precommit checks for
> https://github.com/apache/beam/pull/11156 with the following 6
> commands ?
>
> Run Java PostCommit
> Run Java HadoopFormatIO Performance Test
> Run BigQueryIO Streaming Performance Test Java
> Run Dataflow ValidatesRunner
> Run Spark ValidatesRunner
> Run SQL Postcommit
>
> Regards,
> Tomo
>
>
>

 --
 Regards,
 Tomo

>>>
>>
>> --
>> Regards,
>> Tomo
>>
>>
>
> --
> Regards,
> Tomo
>

>>>
>>> --
>>> Regards,
>>> Tomo
>>>
>>
>
> --
> Regards,
> Tomo
>

Re: Proposal: Beam to use GCP Libraries BOM

[Tomo Suzuki]

Hi Chamikara,

Ahmet is asking for your input in
https://github.com/apache/beam/pull/11156#issuecomment-602716275 . Would
you check this?

On Mon, Mar 23, 2020 at 3:05 PM Tomo Suzuki  wrote:

> (Applied Ahmet's feedback in https://github.com/apache/beam/pull/11156)
>
> Hi Luke,
>
> > the pom files that are produced
>
> Build.gradle that uses the BOM will produce pom files that have
> corresponding dependencies without versions, and have a
> "dependencyManagement" section through which they import the GCP Libraries
> BOM. This fills the versions of the versionless dependencies when build
> systems evaluates the pom files.
>
> > how the GCP BOM impacts the release process
>
> I'm afraid I don't have knowledge on how dependencies affect the Beam
> release process. Would you be willing to break down this concern into some
> questions I can answer?
>
>
>
>
> On Fri, Mar 20, 2020 at 6:13 PM Luke Cwik  wrote:
>
>> My concern would be to validate how the GCP BOM impacts the release
>> process and the pom files that are produced otherwise the next person
>> running a release may run into trouble.
>>
>> On Fri, Mar 20, 2020 at 3:00 PM Pablo Estrada  wrote:
>>
>>> +1
>>>
>>> On Fri, Mar 20, 2020 at 2:41 PM Ismaël Mejía  wrote:
>>>
 Well why we just don't merge it? I am unfamiliar with GCP deps to be
 confident to LGTM it. but given that 22 checks pass and given that
 Tomo addressed most comments and he has already a consistent track of
 good work on dependency improvements I think it is worth to merge it
 as it is. We still have some time to fix stuff if we find any
 regression. WDYT?

 On Thu, Mar 19, 2020 at 9:36 PM Luke Cwik  wrote:
 >
 > As much as I would like to spend time on these reviews, I believe
 I'll be delayed from reviewing them thoroughly till I finish other work
 that I'm targeting for the 2.21 release related to portability. It would be
 greatly appreciated if there are others that could review this in the
 meantime.
 >
 > On Thu, Mar 19, 2020 at 7:09 AM Tomo Suzuki 
 wrote:
 >>
 >> PR is ready (22 successful check)
 >> https://github.com/apache/beam/pull/11156
 >> (Luke assigned himself as a reviewer)
 >>
 >> Regards,
 >> Tomo
 >>
 >> On Wed, Mar 11, 2020 at 3:50 PM Tomo Suzuki 
 wrote:
 >>>
 >>> Thank you for favorable responses. I'll start implementation.
 >>>
 >>> On Thu, Mar 5, 2020 at 2:22 PM Tomo Suzuki 
 wrote:
 
  > Do Spark or Flink have BOMs?
 
  Not that I know of. I couldn't find "bom" in their artifacts [1,
 2].
 
  [1]: https://search.maven.org/search?q=g:org.apache.flink
  [2]: https://search.maven.org/search?q=g:org.apache.spark
 
 
  On Thu, Mar 5, 2020 at 1:46 PM Kenneth Knowles 
 wrote:
 >
 > +1 and you have phrased the benefits and limitations well. We
 have plenty of not-Google-related dependencies that use Guava and protobuf
 (I know of Calcite, Cassandra, Kinesis, and Spark) so there's still work in
 managing deps, but the BOM should make it a lot easier to upgrade all these
 tightly coupled libraries that Google ships from their head.
 >
 > Do Spark or Flink have BOMs? I wonder if there's an opportunity
 to catch incompatible deps at a larger scale by comparing and merging a
 half dozen BOMs (although in the limit it approximately expands to one per
 runner and one per IO and projects mature and become independent)
 >
 > Kenn
 >
 > On Thu, Mar 5, 2020 at 10:05 AM Luke Cwik 
 wrote:
 >>
 >> How would the Apache Beam BOM and GCP BOM work together?
 >>
 >> On Thu, Mar 5, 2020 at 7:25 AM Filipe Regadas <
 filiperega...@gmail.com> wrote:
 >>>
 >>> Big +1, this is a step in the right direction and checking with
 other Beam's direct and transitive deps is crucial since the referred bom
 only convers a small part of it. Apache Commons, Jackson, `com.google.{api,
 apis, cloud}`, slf4j comes to mind.
 >>>
 >>> Filipe Regadas
 >>>
 >>>
 >>> On Thu, Mar 5, 2020 at 3:33 AM Ismaël Mejía 
 wrote:
 
  +1 Sounds like a good improvement for users and maintainers !
 
  On Thu, Mar 5, 2020 at 6:59 AM Alex Van Boxel <
 a...@vanboxel.be> wrote:
  >
  > +1, I can remember the countless hours that we fought with
 Google dependencies.
  >
  > On Thu, Mar 5, 2020, 04:07 Chamikara Jayalath <
 chamik...@google.com> wrote:
  >>
  >> +1 for this.
  >>
  >> This will make life easy for many of our users and will
 help us keep GCP related dependencies compatible (which has not been easy
 in the past).
  >>
  

Re: Jenkins jobs not running for my PR 10438

[Tomo Suzuki]

Hi Beam committers,
(Thanks Ahmet)

Would you retrigger the following 5 jobs for
https://github.com/apache/beam/pull/11156 ?
Run Dataflow ValidatesRunner
Run Java PreCommit
Run Portable_Python PreCommit
Run PythonFormatter PreCommit
Run Website PreCommit


On Thu, Mar 26, 2020 at 9:45 PM Ahmet Altay  wrote:

> Done.
>
> On Thu, Mar 26, 2020 at 2:37 PM Tomo Suzuki  wrote:
>
>> Hi Beam committers,
>> (Thanks Ahmet for previous attempt)
>>
>> Would you trigger
>> - The failed "Run Java Precommit" for
>> https://github.com/apache/beam/pull/11208,
>> - and the precommit checks for https://github.com/apache/beam/pull/11156  
>> with
>> the following 6 checks?
>> Run Java PostCommit
>> Run Java HadoopFormatIO Performance Test
>> Run BigQueryIO Streaming Performance Test Java
>> Run Dataflow ValidatesRunner
>> Run Spark ValidatesRunner
>> Run SQL Postcommit
>>
>> On Tue, Mar 24, 2020 at 6:37 PM Ahmet Altay  wrote:
>>
>>> KInd of done. 11208 is running the tests. 11156 did not start all the
>>> tests. Someone could retry that again in a bit.
>>>
>>> On Tue, Mar 24, 2020 at 12:11 PM Tomo Suzuki  wrote:
>>>
 Hi Beam committers,

 Would you trigger precommit checks for
 https://github.com/apache/beam/pull/11156 and
 https://github.com/apache/beam/pull/11208 with the following 6 checks?
 Run Java PostCommit
 Run Java HadoopFormatIO Performance Test
 Run BigQueryIO Streaming Performance Test Java
 Run Dataflow ValidatesRunner
 Run Spark ValidatesRunner
 Run SQL Postcommit


 On Fri, Mar 20, 2020 at 11:13 AM Jan Lukavský  wrote:

> Hi, done.
> On 3/20/20 3:59 PM, Tomo Suzuki wrote:
>
> HI Beam committers,
> (Thanks Ahmet)
>
> Would you re-run the presubmit checks for
> https://github.com/apache/beam/pull/11168 with the followings?
> Run Java PostCommit
> Run Java HadoopFormatIO Performance Test
> Run BigQueryIO Streaming Performance Test Java
> Run Dataflow ValidatesRunner
> Run Spark ValidatesRunner
> Run SQL Postcommit
>
>
> On Wed, Mar 18, 2020 at 9:09 PM Ahmet Altay  wrote:
>
>> Done.
>>
>> On Wed, Mar 18, 2020 at 5:57 PM Tomo Suzuki 
>> wrote:
>>
>>> Hi Beam committers,
>>> (Alexey, thank you!)
>>>
>>> 1. Would you run the 2 failed checks Java PreCommit and Python
>>> PreCommit for https://github.com/apache/beam/pull/11156
>>>
>>> 2. Would you run the precommit checks for
>>> https://github.com/apache/beam/pull/11168 with the following 6
>>> commands?
>>> Run Java PostCommit
>>> Run Java HadoopFormatIO Performance Test
>>> Run BigQueryIO Streaming Performance Test Java
>>> Run Dataflow ValidatesRunner
>>> Run Spark ValidatesRunner
>>> Run SQL Postcommit
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Mar 18, 2020 at 1:08 PM Alexey Romanenko <
>>> aromanenko@gmail.com> wrote:
>>>
 Done

 On 18 Mar 2020, at 15:25, Tomo Suzuki  wrote:

 Hi Beam committers,

 Would you trigger the precommit checks for
 https://github.com/apache/beam/pull/11156 with the following 6
 commands ?

 Run Java PostCommit
 Run Java HadoopFormatIO Performance Test
 Run BigQueryIO Streaming Performance Test Java
 Run Dataflow ValidatesRunner
 Run Spark ValidatesRunner
 Run SQL Postcommit

 Regards,
 Tomo



>>>
>>> --
>>> Regards,
>>> Tomo
>>>
>>
>
> --
> Regards,
> Tomo
>
>

 --
 Regards,
 Tomo

>>>
>>
>> --
>> Regards,
>> Tomo
>>
>

-- 
Regards,
Tomo

Re: [DISCUSS] [PROPOSAL] Redesigning the structure for Beam docs

[Cyrus Maden]

This is way cool! Big fan of the new table of content, too. I also like the
future content experience plans. Having a documented path for new
contributors (core SDK, website, all of it) will be great.

On Fri, Mar 27, 2020 at 4:58 PM Kenneth Knowles  wrote:

> Wow, this looks so much better. Even just reading the new table of
> contents for the site I am convinced it will be much more useful. Made a
> couple comments of things that maybe were introduced since the work
> started, or just missing from the table of contents.
>
> Kenn
>
> On Thu, Mar 26, 2020 at 3:31 PM Rose Nguyen  wrote:
>
>> Hi there,
>>
>> As part of the documentation revamping process [1] and ongoing website
>> migration [2] [3], Aizhamal, David, and I would like to propose this website
>> redesign
>> 
>> [4]. It lists the rationale and proposed layout that we believe, after
>> collecting feedback and brainstorming with various Beam users/community
>> members, will improve the usability of Beam.
>>
>> We'd like to share this design plan as we begin to finalize it. If you
>> have feedback or comments, we'd like to hear from you!
>>
>> [1]
>> https://docs.google.com/document/d/1HlRHfmc9MvKkFEf2gfIL3RYVxTmBXQL4sXjAGGOjeiI/edit#heading=h.5rqdbnson7px
>> [2]
>> https://lists.apache.org/thread.html/rfab4cc1411318c3f4667bee051df68f37be11846ada877f3576c41a9%40%3Cdev.beam.apache.org%3E
>> [3]
>>
>> https://lists.apache.org/thread.html/r7fa6d710c0a1959cce5108e460d71c306ce5756cf96af818b41cb7ca%40%3Cdev.beam.apache.org%3E
>> [4]
>> https://docs.google.com/document/d/1btXMkQGqYaU9pUjYh0iCNrbXf4pAHe3tBFsLQ_cLYHg/edit?usp=sharing
>>
>> Stay well,
>> --
>> Rose Thị Nguyễn
>>
>

Beam Dependency Check Report (2020-03-30)

[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
  
google-cloud-datastore
1.7.4
1.11.0
2019-05-27
2020-03-24BEAM-8443
google-cloud-pubsub
1.0.2
1.4.2
2019-12-23
2020-03-30BEAM-5539
google-cloud-vision
0.42.0
1.0.0
2020-03-24
2020-03-24BEAM-9581
grpcio-tools
1.14.2
1.27.2
2020-03-24
2020-03-24BEAM-9582
httplib2
0.12.0
0.17.0
2018-12-10
2020-01-27BEAM-9018
mock
2.0.0
3.0.5
2019-05-20
2019-05-20BEAM-7369
oauth2client
3.0.0
4.1.3
2018-12-10
2018-12-10BEAM-6089
prompt-toolkit
1.0.18
2.0.10
2020-03-24
2020-03-24BEAM-9583
tenacity
5.1.5
6.1.0
2019-11-11
2020-03-24BEAM-8607
tox
3.11.1
3.14.6
2020-03-24
2020-03-30BEAM-9584
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.alibaba:fastjson
1.2.49
1.2.68
2018-08-04
2020-03-28BEAM-8632
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-RC5
2018-03-20
2020-03-08BEAM-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.20.0
0.28.0
2019-02-11
2020-02-24BEAM-6645
com.github.luben:zstd-jni
1.3.8-3
1.4.4-9
2019-01-29
2020-03-27BEAM-9194
com.github.spotbugs:spotbugs
3.1.12
4.0.1
2019-03-01
2020-03-18BEAM-7792
com.github.spotbugs:spotbugs-annotations
3.1.12
4.0.1
2019-03-01
2020-03-18BEAM-6951
com.google.api.grpc:grpc-google-common-protos
1.12.0
1.17.0
2018-06-29
2019-10-04BEAM-8633
com.google.api.grpc:proto-google-cloud-bigquerystorage-v1beta1
0.85.1
0.91.0
2020-01-08
2020-03-10BEAM-8678
com.google.api.grpc:proto-google-cloud-spanner-admin-database-v1
1.49.1
1.52.0
2020-01-28
2020-03-20BEAM-8682
com.google.api.grpc:proto-google-common-protos
1.12.0
1.17.0
2018-06-29
2019-10-04BEAM-6899
com.google.apis:google-api-services-clouddebugger
v2-rev20191003-1.30.3
v2-rev20200313-1.30.9
2019-10-19
2020-03-24BEAM-8750
com.google.apis:google-api-services-cloudresourcemanager
v1-rev20191206-1.30.3
v2-rev20200210-1.30.9
2019-12-17
2020-03-05BEAM-8751
com.google.apis:google-api-services-dataflow
v1b3-rev20190927-1.30.3
v1beta3-rev12-1.20.0
2019-10-11
2015-04-29BEAM-8752
com.google.apis:google-api-services-pubsub
v1-rev2019-1.30.3
v1-rev20200312-1.30.9
2019-11-26
2020-03-24BEAM-8753
com.google.apis:google-api-services-storage
v1-rev20191011-1.30.3
v1-rev20200226-1.30.9
2019-10-30
2020-03-16BEAM-8754
com.google.cloud:google-cloud-spanner
1.49.1
1.52.0
2020-01-28
2020-03-20BEAM-8758
com.google.guava:guava-testlib
25.1-jre
28.2-jre
2018-05-23
2019-12-27BEAM-8760
com.google.protobuf.nano:protobuf-javanano
3.0.0-alpha-5
3.2.0rc2
2016-01-06
2017-01-19BEAM-9098
com.gradle.build-scan:com.gradle.build-scan.gradle.plugin
2.3
3.2
2019-05-20
2020-03-30BEAM-6647
com.hazelcast:hazelcast
3.12
4.0
2019-04-09
2020-02-04BEAM-8636
com.hazelcast.jet:hazelcast-jet
3.0
4.0
2019-04-11
2020-03-02BEAM-9586
com.hazelcast.jet:hazelcast-jet-core
3.0
4.0
2019-04-11
2020-03-02BEAM-9587
com.ning:compress-lzf
1.0.3
1.0.4
2014-08-16
2017-03-14BEAM-9100
com.pholser:junit-quickcheck-core
0.8
0.9.1
2018-03-08
2020-01-21BEAM-8699
io.netty:netty-handler
4.1.30.Final
5.0.0.Alpha2
2018-09-27
2015-03-03BEAM-8703