Re: PipelineOptions fromSystemProps?

[Romain Manni-Bucau]

2018-02-15 20:00 GMT+01:00 Kenneth Knowles :

> On Thu, Feb 15, 2018 at 12:03 AM, Romain Manni-Bucau <
> rmannibu...@gmail.com> wrote:
>>
>> 2. default properties = env + system properties: this is what all config
>> libs do (spring config, tamaya, deltaspike, microprofile-config, ...) so it
>> is very comfortable and sane for end users. It enables ops (env) and dev
>> (system properties) to feel comfortable for free with this and avoids us to
>> have N entry points which has the nice side effect to consolidate the
>> overall consistency of the framework/lib.
>>
>
> Can you link to the docs for these examples? I'm sure we'd like to learn
> from them.
>

I'm not the best to find docs but the relevant bits are:

https://github.com/apache/deltaspike/blob/842c84bd1767905a19e2af01bdfe88d416d1b2da/deltaspike/core/impl/src/main/java/org/apache/deltaspike/core/impl/config/DefaultConfigSourceProvider.java#L57
https://github.com/apache/geronimo-config/blob/trunk/impl/src/main/java/org/apache/geronimo/config/DefaultConfigBuilder.java#L182
https://github.com/spring-projects/spring-framework/blob/a0bce618c2f51d8af1fc00ee2c3868ba2c8e0045/spring-core/src/main/java/org/springframework/core/env/StandardEnvironment.java#L78

(and there are others a bit less mainstream)

The point is just that it is very common to read both and would be weird to
not have that feature if we read from system props.


>
>
>> 4. support null: I'd like to support null as a valid valid for
>> properties. The rational here is to make it neat for end user and support:
>> fromProperties(loadProps()) with a loadProps in the user codebase which can
>> return null. We just default to create(). For us it iss pretty much nothing
>> but it enables end users to not care about it. Concretely one null check
>> versus millions (or thousands at least ;)).
>>
>
> https://www.infoq.com/presentations/Null-References-
> The-Billion-Dollar-Mistake-Tony-Hoare
>

:), concretely this applies only to your own codebase, as soon as you start
to expose an external API (intended pleonasm ;)) then you are forced to
handle null cause you can't help users to pass null. It doesn't imply for
all API in beam, for instance @ProcessElement can assume it is not null in
several cases but this fromXXX() is 100% delegated to the users. Here the
compromise is the cost of handling it once for all vs the cost to ask all
users to do it. My opinion is that it doesnt cost anything for beam, it is
safe for beam and therefore it is way better to put it in beam than ask all
users to care about it.

That said I don't want to spend my week spare time speaking of that since
the feature is straight forward and not impacting the runtime. This is why
i droppped it from this PR.


>
> Kenn
>

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

[Jean-Baptiste Onofré]

Great !!!

Thanks for the update, I will close the vote then.

Regards
JB

On 02/15/2018 11:45 PM, Ben Sidhom wrote:
> I just successfully ran the quickstart on Flink 1.4.0 on Dataproc. Should be
> good to go.
> 
> 
> On Thu, Feb 15, 2018 at 9:21 AM Jean-Baptiste Onofré  > wrote:
> 
> Luke said he tested Flink locally. So, we have to test on a Yarn cluster.
> 
> Regards
> JB
> 
> On 02/15/2018 06:16 PM, Reuven Lax wrote:
> > I count enough votes :) So sounds like someone needs to verify Flink 1.4
> > quickstart, and then we're ready?
> >
> > On Wed, Feb 14, 2018 at 5:38 PM, Robert Bradshaw  
> > >> wrote:
> >
> >     +1 (binding) pending Flink verification. I have checked the 
> signatures
> >     and checksums of the artifacts, and that it agrees with commit
> >     67b5e1bab25d284cdac2127b47f44acc8e83499e on github *except* for 76
> >     places where -SNAPSHOT was removed.
> >
> >     FWIW, http://www.apache.org/dev/release-distribution
> >      now recommends
> >     sha512 (over sha1 which has been broken).
> >
> >     On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov
> 
> >     >> wrote:
> >     > Thanks Kenn. I retract my -1, but then someone must verify it 
> with Flink
> >     > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on 
> Dataproc).
> >     >
> >     > On Wed, Feb 14, 2018 at 4:53 PM Reuven Lax  
> >     >> wrote:
> >     >>
> >     >> +1 (binding)
> >     >>
> >     >> On Wed, Feb 14, 2018 at 10:42 AM, Alan Myrvold 
>  
> >     >>
> >     >> wrote:
> >     >>>
> >     >>> +1 Validated java quickstarts for direct, dataflow, apex, 
> flink, and
> >     >>> spark.
> >     >>>
> >     >>> On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik  
> >     >> wrote:
> >     
> >      +1 (binding)
> >      Validated several quickstarts including the regression that I
> originally
> >      reported with Spark.
> >     
> >      On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía 
>  
> >     >> wrote:
> >     >
> >     > +1 (binding)
> >     >
> >     > Validated SHAs + tag vs source.zip file.
> >     > Run mvn clean install -Prelease OK
> >     > Validated that the 3 regressions reported for RC1 were fixed.
> >     > Run Nexmark on Direct/Flink runner on local mode, no 
> regressions
> now.
> >     > Installed python version on virtualenv and run local 
> wordcount with
> >     > success.
> >     > Checked that the hadoop-input-format artifact is in the 
> extended
> >     > staging area.
> >     >
> >     > On Tue, Feb 13, 2018 at 5:41 PM, Jean-Baptiste Onofré
> 
> >     >>
> >     > wrote:
> >     > > +1 (binding)
> >     > >
> >     > > Tested the Spark runner (with wordcount example and beam 
> samples)
> >     > > Tested the performance of the direct runner
> >     > >
> >     > > I just updated the spreadsheet.
> >     > >
> >     > > Regards
> >     > > JB
> >     > >
> >     > > On 02/11/2018 06:33 AM, Jean-Baptiste Onofré wrote:
> >     > >> Hi everyone,
> >     > >>
> >     > >> Please review and vote on the release candidate #3 for the
> version
> >     > >> 2.3.0, as
> >     > >> follows:
> >     > >>
> >     > >> [ ] +1, Approve the release
> >     > >> [ ] -1, Do not approve the release (please provide specific
> >     > >> comments)
> >     > >>
> >     > >>
> >     > >> The complete staging area is available for your review, 
> which
> >     > >> includes:
> >     > >> * JIRA release notes [1],
> >     > >> * the official Apache source release to be deployed to
> >     > >> dist.apache.org 
>  [2],
> >     > >> which is signed with the key with fingerprint C8282E76 [3],
> > 

Re: [PROPOSAL] Switch from Guava futures vs Java 8 futures

[Kenneth Knowles]

For anyone just following the dev list, this is completed.

On Fri, Feb 2, 2018 at 12:34 AM, Holden Karau  wrote:

> For what it's worth there exists a relatively easy Java8 to Scala future
> conversion so this shouldn't cause an issue on the Spark runner.
>
> On Thu, Feb 1, 2018 at 11:22 PM, Alexey Romanenko <
> aromanenko@gmail.com> wrote:
>
>> +1, sounds great!
>>
>> Regards,
>> Alexey
>>
>>
>> On 2 Feb 2018, at 07:14, Thomas Weise  wrote:
>>
>> +1
>>
>>
>> On Thu, Feb 1, 2018 at 9:07 PM, Jean-Baptiste Onofré 
>> wrote:
>>
>>> +1
>>>
>>> Regards
>>> JB
>>>
>>> On 02/01/2018 07:54 PM, Kenneth Knowles wrote:
>>> > Hi all,
>>> >
>>> > Luke, Thomas, and I had some in-person discussions about the use of
>>> Java 8
>>> > futures and Guava futures in the portability support code. I wanted to
>>> bring our
>>> > thoughts to the dev list for feedback.
>>> >
>>> > As background:
>>> >
>>> >  - Java 5+ "Future" lacks the main purpose of future, which is async
>>> chaining.
>>> >  - Guava introduced ListenableFuture to do real future-oriented
>>> programming
>>> >  - Java 8 added CompletionStage which is more-or-less the expected
>>> interface
>>> >
>>> > It is still debatable whether Java got it right [1]. But since it is
>>> > standardized, doesn't need to be shaded, etc, it is worth trying to
>>> just use it
>>> > carefully in the right ways. So we thought to propose that we migrate
>>> most uses
>>> > of Guava futures to Java 8 futures.
>>> >
>>> > What do you think? Have we missed an important problem that would make
>>> this a
>>> > deal-breaker?
>>> >
>>> > Kenn
>>> >
>>> > [1]
>>> > e.g. https://stackoverflow.com/questions/38744943/listenable
>>> future-vs-completablefuture#comment72041244_39250452
>>> > and such discussions are likely to occur whenever you bring it up with
>>> someone
>>> > who cares a lot about futures :-)
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>
>
> --
> Twitter: https://twitter.com/holdenkarau
>

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

[Reuven Lax]

Thanks! Sounds like third RC is the winner :)

On Thu, Feb 15, 2018 at 2:45 PM, Ben Sidhom  wrote:

> I just successfully ran the quickstart on Flink 1.4.0 on Dataproc. Should
> be good to go.
>
>
> On Thu, Feb 15, 2018 at 9:21 AM Jean-Baptiste Onofré 
> wrote:
>
>> Luke said he tested Flink locally. So, we have to test on a Yarn cluster.
>>
>> Regards
>> JB
>>
>> On 02/15/2018 06:16 PM, Reuven Lax wrote:
>> > I count enough votes :) So sounds like someone needs to verify Flink 1.4
>> > quickstart, and then we're ready?
>> >
>> > On Wed, Feb 14, 2018 at 5:38 PM, Robert Bradshaw > > > wrote:
>> >
>> > +1 (binding) pending Flink verification. I have checked the
>> signatures
>> > and checksums of the artifacts, and that it agrees with commit
>> > 67b5e1bab25d284cdac2127b47f44acc8e83499e on github *except* for 76
>> > places where -SNAPSHOT was removed.
>> >
>> > FWIW, http://www.apache.org/dev/release-distribution
>> >  now recommends
>> > sha512 (over sha1 which has been broken).
>> >
>> > On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov <
>> kirpic...@google.com
>> > > wrote:
>> > > Thanks Kenn. I retract my -1, but then someone must verify it
>> with Flink
>> > > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on
>> Dataproc).
>> > >
>> > > On Wed, Feb 14, 2018 at 4:53 PM Reuven Lax > > > wrote:
>> > >>
>> > >> +1 (binding)
>> > >>
>> > >> On Wed, Feb 14, 2018 at 10:42 AM, Alan Myrvold <
>> amyrv...@google.com
>> > >
>> > >> wrote:
>> > >>>
>> > >>> +1 Validated java quickstarts for direct, dataflow, apex,
>> flink, and
>> > >>> spark.
>> > >>>
>> > >>> On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik > > > wrote:
>> > 
>> >  +1 (binding)
>> >  Validated several quickstarts including the regression that I
>> originally
>> >  reported with Spark.
>> > 
>> >  On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía <
>> ieme...@gmail.com
>> > > wrote:
>> > >
>> > > +1 (binding)
>> > >
>> > > Validated SHAs + tag vs source.zip file.
>> > > Run mvn clean install -Prelease OK
>> > > Validated that the 3 regressions reported for RC1 were fixed.
>> > > Run Nexmark on Direct/Flink runner on local mode, no
>> regressions now.
>> > > Installed python version on virtualenv and run local
>> wordcount with
>> > > success.
>> > > Checked that the hadoop-input-format artifact is in the
>> extended
>> > > staging area.
>> > >
>> > > On Tue, Feb 13, 2018 at 5:41 PM, Jean-Baptiste Onofré <
>> j...@nanthrax.net
>> > >
>> > > wrote:
>> > > > +1 (binding)
>> > > >
>> > > > Tested the Spark runner (with wordcount example and beam
>> samples)
>> > > > Tested the performance of the direct runner
>> > > >
>> > > > I just updated the spreadsheet.
>> > > >
>> > > > Regards
>> > > > JB
>> > > >
>> > > > On 02/11/2018 06:33 AM, Jean-Baptiste Onofré wrote:
>> > > >> Hi everyone,
>> > > >>
>> > > >> Please review and vote on the release candidate #3 for the
>> version
>> > > >> 2.3.0, as
>> > > >> follows:
>> > > >>
>> > > >> [ ] +1, Approve the release
>> > > >> [ ] -1, Do not approve the release (please provide specific
>> > > >> comments)
>> > > >>
>> > > >>
>> > > >> The complete staging area is available for your review,
>> which
>> > > >> includes:
>> > > >> * JIRA release notes [1],
>> > > >> * the official Apache source release to be deployed to
>> > > >> dist.apache.org  [2],
>> > > >> which is signed with the key with fingerprint C8282E76 [3],
>> > > >> * all artifacts to be deployed to the Maven Central
>> Repository [4],
>> > > >> * source code tag "v2.3.0-RC3" [5],
>> > > >> * website pull request listing the release and publishing
>> the API
>> > > >> reference
>> > > >> manual [6].
>> > > >> * Java artifacts were built with Maven 3.3.9 and Oracle JDK
>> > > >> 1.8.0_111.
>> > > >> * Python artifacts are deployed along with the source
>> release to the
>> > > >> dist.apache.org  [2].
>> > > >>
>> > > >> The vote will be open for at least 72 hours. It is adopted
>> by
>> > > >> majority approval,
>> > > >> with at least 3 PMC affirmative votes.
>> > > >>

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

[Ben Sidhom]

I just successfully ran the quickstart on Flink 1.4.0 on Dataproc. Should
be good to go.


On Thu, Feb 15, 2018 at 9:21 AM Jean-Baptiste Onofré 
wrote:

> Luke said he tested Flink locally. So, we have to test on a Yarn cluster.
>
> Regards
> JB
>
> On 02/15/2018 06:16 PM, Reuven Lax wrote:
> > I count enough votes :) So sounds like someone needs to verify Flink 1.4
> > quickstart, and then we're ready?
> >
> > On Wed, Feb 14, 2018 at 5:38 PM, Robert Bradshaw  > > wrote:
> >
> > +1 (binding) pending Flink verification. I have checked the
> signatures
> > and checksums of the artifacts, and that it agrees with commit
> > 67b5e1bab25d284cdac2127b47f44acc8e83499e on github *except* for 76
> > places where -SNAPSHOT was removed.
> >
> > FWIW, http://www.apache.org/dev/release-distribution
> >  now recommends
> > sha512 (over sha1 which has been broken).
> >
> > On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov <
> kirpic...@google.com
> > > wrote:
> > > Thanks Kenn. I retract my -1, but then someone must verify it with
> Flink
> > > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on
> Dataproc).
> > >
> > > On Wed, Feb 14, 2018 at 4:53 PM Reuven Lax  > > wrote:
> > >>
> > >> +1 (binding)
> > >>
> > >> On Wed, Feb 14, 2018 at 10:42 AM, Alan Myrvold <
> amyrv...@google.com
> > >
> > >> wrote:
> > >>>
> > >>> +1 Validated java quickstarts for direct, dataflow, apex, flink,
> and
> > >>> spark.
> > >>>
> > >>> On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik  > > wrote:
> > 
> >  +1 (binding)
> >  Validated several quickstarts including the regression that I
> originally
> >  reported with Spark.
> > 
> >  On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía <
> ieme...@gmail.com
> > > wrote:
> > >
> > > +1 (binding)
> > >
> > > Validated SHAs + tag vs source.zip file.
> > > Run mvn clean install -Prelease OK
> > > Validated that the 3 regressions reported for RC1 were fixed.
> > > Run Nexmark on Direct/Flink runner on local mode, no
> regressions now.
> > > Installed python version on virtualenv and run local wordcount
> with
> > > success.
> > > Checked that the hadoop-input-format artifact is in the
> extended
> > > staging area.
> > >
> > > On Tue, Feb 13, 2018 at 5:41 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net
> > >
> > > wrote:
> > > > +1 (binding)
> > > >
> > > > Tested the Spark runner (with wordcount example and beam
> samples)
> > > > Tested the performance of the direct runner
> > > >
> > > > I just updated the spreadsheet.
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 02/11/2018 06:33 AM, Jean-Baptiste Onofré wrote:
> > > >> Hi everyone,
> > > >>
> > > >> Please review and vote on the release candidate #3 for the
> version
> > > >> 2.3.0, as
> > > >> follows:
> > > >>
> > > >> [ ] +1, Approve the release
> > > >> [ ] -1, Do not approve the release (please provide specific
> > > >> comments)
> > > >>
> > > >>
> > > >> The complete staging area is available for your review,
> which
> > > >> includes:
> > > >> * JIRA release notes [1],
> > > >> * the official Apache source release to be deployed to
> > > >> dist.apache.org  [2],
> > > >> which is signed with the key with fingerprint C8282E76 [3],
> > > >> * all artifacts to be deployed to the Maven Central
> Repository [4],
> > > >> * source code tag "v2.3.0-RC3" [5],
> > > >> * website pull request listing the release and publishing
> the API
> > > >> reference
> > > >> manual [6].
> > > >> * Java artifacts were built with Maven 3.3.9 and Oracle JDK
> > > >> 1.8.0_111.
> > > >> * Python artifacts are deployed along with the source
> release to the
> > > >> dist.apache.org  [2].
> > > >>
> > > >> The vote will be open for at least 72 hours. It is adopted
> by
> > > >> majority approval,
> > > >> with at least 3 PMC affirmative votes.
> > > >>
> > > >> Thanks,
> > > >> JB
> > > >>
> > > >> [1]
> > > >>
> > > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
> > <
> 

Re: PipelineOptions fromSystemProps?

[Kenneth Knowles]

On Thu, Feb 15, 2018 at 12:03 AM, Romain Manni-Bucau 
wrote:
>
> 2. default properties = env + system properties: this is what all config
> libs do (spring config, tamaya, deltaspike, microprofile-config, ...) so it
> is very comfortable and sane for end users. It enables ops (env) and dev
> (system properties) to feel comfortable for free with this and avoids us to
> have N entry points which has the nice side effect to consolidate the
> overall consistency of the framework/lib.
>

Can you link to the docs for these examples? I'm sure we'd like to learn
from them.


> 4. support null: I'd like to support null as a valid valid for properties.
> The rational here is to make it neat for end user and support:
> fromProperties(loadProps()) with a loadProps in the user codebase which can
> return null. We just default to create(). For us it iss pretty much nothing
> but it enables end users to not care about it. Concretely one null check
> versus millions (or thousands at least ;)).
>

https://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare

Kenn

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

[Jean-Baptiste Onofré]

Luke said he tested Flink locally. So, we have to test on a Yarn cluster.

Regards
JB

On 02/15/2018 06:16 PM, Reuven Lax wrote:
> I count enough votes :) So sounds like someone needs to verify Flink 1.4
> quickstart, and then we're ready?
> 
> On Wed, Feb 14, 2018 at 5:38 PM, Robert Bradshaw  > wrote:
> 
> +1 (binding) pending Flink verification. I have checked the signatures
> and checksums of the artifacts, and that it agrees with commit
> 67b5e1bab25d284cdac2127b47f44acc8e83499e on github *except* for 76
> places where -SNAPSHOT was removed.
> 
> FWIW, http://www.apache.org/dev/release-distribution
>  now recommends
> sha512 (over sha1 which has been broken).
> 
> On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov  > wrote:
> > Thanks Kenn. I retract my -1, but then someone must verify it with Flink
> > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on Dataproc).
> >
> > On Wed, Feb 14, 2018 at 4:53 PM Reuven Lax  > wrote:
> >>
> >> +1 (binding)
> >>
> >> On Wed, Feb 14, 2018 at 10:42 AM, Alan Myrvold  >
> >> wrote:
> >>>
> >>> +1 Validated java quickstarts for direct, dataflow, apex, flink, and
> >>> spark.
> >>>
> >>> On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik  > wrote:
> 
>  +1 (binding)
>  Validated several quickstarts including the regression that I 
> originally
>  reported with Spark.
> 
>  On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía  > wrote:
> >
> > +1 (binding)
> >
> > Validated SHAs + tag vs source.zip file.
> > Run mvn clean install -Prelease OK
> > Validated that the 3 regressions reported for RC1 were fixed.
> > Run Nexmark on Direct/Flink runner on local mode, no regressions 
> now.
> > Installed python version on virtualenv and run local wordcount with
> > success.
> > Checked that the hadoop-input-format artifact is in the extended
> > staging area.
> >
> > On Tue, Feb 13, 2018 at 5:41 PM, Jean-Baptiste Onofré 
>  >
> > wrote:
> > > +1 (binding)
> > >
> > > Tested the Spark runner (with wordcount example and beam samples)
> > > Tested the performance of the direct runner
> > >
> > > I just updated the spreadsheet.
> > >
> > > Regards
> > > JB
> > >
> > > On 02/11/2018 06:33 AM, Jean-Baptiste Onofré wrote:
> > >> Hi everyone,
> > >>
> > >> Please review and vote on the release candidate #3 for the 
> version
> > >> 2.3.0, as
> > >> follows:
> > >>
> > >> [ ] +1, Approve the release
> > >> [ ] -1, Do not approve the release (please provide specific
> > >> comments)
> > >>
> > >>
> > >> The complete staging area is available for your review, which
> > >> includes:
> > >> * JIRA release notes [1],
> > >> * the official Apache source release to be deployed to
> > >> dist.apache.org  [2],
> > >> which is signed with the key with fingerprint C8282E76 [3],
> > >> * all artifacts to be deployed to the Maven Central Repository 
> [4],
> > >> * source code tag "v2.3.0-RC3" [5],
> > >> * website pull request listing the release and publishing the API
> > >> reference
> > >> manual [6].
> > >> * Java artifacts were built with Maven 3.3.9 and Oracle JDK
> > >> 1.8.0_111.
> > >> * Python artifacts are deployed along with the source release to 
> the
> > >> dist.apache.org  [2].
> > >>
> > >> The vote will be open for at least 72 hours. It is adopted by
> > >> majority approval,
> > >> with at least 3 PMC affirmative votes.
> > >>
> > >> Thanks,
> > >> JB
> > >>
> > >> [1]
> > >>
> > >>
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12341608
> 
> 
> > >> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> 
> > >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> 
> > >> [4]
> > >>
> 

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

[Reuven Lax]

I count enough votes :) So sounds like someone needs to verify Flink 1.4
quickstart, and then we're ready?

On Wed, Feb 14, 2018 at 5:38 PM, Robert Bradshaw 
wrote:

> +1 (binding) pending Flink verification. I have checked the signatures
> and checksums of the artifacts, and that it agrees with commit
> 67b5e1bab25d284cdac2127b47f44acc8e83499e on github *except* for 76
> places where -SNAPSHOT was removed.
>
> FWIW, http://www.apache.org/dev/release-distribution now recommends
> sha512 (over sha1 which has been broken).
>
> On Wed, Feb 14, 2018 at 5:24 PM, Eugene Kirpichov 
> wrote:
> > Thanks Kenn. I retract my -1, but then someone must verify it with Flink
> > 1.4. I might give it a shot tomorrow (installing Flink 1.4 on Dataproc).
> >
> > On Wed, Feb 14, 2018 at 4:53 PM Reuven Lax  wrote:
> >>
> >> +1 (binding)
> >>
> >> On Wed, Feb 14, 2018 at 10:42 AM, Alan Myrvold 
> >> wrote:
> >>>
> >>> +1 Validated java quickstarts for direct, dataflow, apex, flink, and
> >>> spark.
> >>>
> >>> On Wed, Feb 14, 2018 at 9:21 AM, Lukasz Cwik  wrote:
> 
>  +1 (binding)
>  Validated several quickstarts including the regression that I
> originally
>  reported with Spark.
> 
>  On Wed, Feb 14, 2018 at 5:34 AM, Ismaël Mejía 
> wrote:
> >
> > +1 (binding)
> >
> > Validated SHAs + tag vs source.zip file.
> > Run mvn clean install -Prelease OK
> > Validated that the 3 regressions reported for RC1 were fixed.
> > Run Nexmark on Direct/Flink runner on local mode, no regressions now.
> > Installed python version on virtualenv and run local wordcount with
> > success.
> > Checked that the hadoop-input-format artifact is in the extended
> > staging area.
> >
> > On Tue, Feb 13, 2018 at 5:41 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > wrote:
> > > +1 (binding)
> > >
> > > Tested the Spark runner (with wordcount example and beam samples)
> > > Tested the performance of the direct runner
> > >
> > > I just updated the spreadsheet.
> > >
> > > Regards
> > > JB
> > >
> > > On 02/11/2018 06:33 AM, Jean-Baptiste Onofré wrote:
> > >> Hi everyone,
> > >>
> > >> Please review and vote on the release candidate #3 for the version
> > >> 2.3.0, as
> > >> follows:
> > >>
> > >> [ ] +1, Approve the release
> > >> [ ] -1, Do not approve the release (please provide specific
> > >> comments)
> > >>
> > >>
> > >> The complete staging area is available for your review, which
> > >> includes:
> > >> * JIRA release notes [1],
> > >> * the official Apache source release to be deployed to
> > >> dist.apache.org [2],
> > >> which is signed with the key with fingerprint C8282E76 [3],
> > >> * all artifacts to be deployed to the Maven Central Repository
> [4],
> > >> * source code tag "v2.3.0-RC3" [5],
> > >> * website pull request listing the release and publishing the API
> > >> reference
> > >> manual [6].
> > >> * Java artifacts were built with Maven 3.3.9 and Oracle JDK
> > >> 1.8.0_111.
> > >> * Python artifacts are deployed along with the source release to
> the
> > >> dist.apache.org [2].
> > >>
> > >> The vote will be open for at least 72 hours. It is adopted by
> > >> majority approval,
> > >> with at least 3 PMC affirmative votes.
> > >>
> > >> Thanks,
> > >> JB
> > >>
> > >> [1]
> > >>
> > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319527=12341608
> > >> [2] https://dist.apache.org/repos/dist/dev/beam/2.3.0/
> > >> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
> > >> [4]
> > >> https://repository.apache.org/content/repositories/
> orgapachebeam-1028/
> > >> [5] https://github.com/apache/beam/tree/v2.3.0-RC3
> > >> [6] https://github.com/apache/beam-site/pull/381
> > >>
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> 
> 
> >>>
> >
>