Another quick update.

Aviem updated the Jira as he and his team wants to take a look. I'm also doing a new bisect on my side. I've given an extra day to move forward. If we don't have clear statement tonight, then, I will cut the RC3 tonight or tomorrow morning (my time).


On 08/05/2017 02:37 AM, Eugene Kirpichov wrote:
I did some more investigation on that JIRA and my conclusion is:

We need to postpone that JIRA to 2.2.0 and finalize release 2.1.0 as-is.

The TL;DR of my investigation is that:
- We have some confidence that Spark runner in 2.1.0 generally works
properly: it passes ValidatesRunner tests, and there's been some amount of
manual testing.
- Release 2.0.0 does not contain a critical fix and, if I understand
correctly, Spark runner at 2.0.0 was basically unusable in streaming
cluster mode.
- So, even if the JIRA signals that there is something wrong in the Spark
runner at 2.1.0, it's definitely better than 2.0.0 so there is no
regression for the user.

I moved the JIRA to 2.2.0 so there are no blocking issues remaining for
2.1.0. JB - the next step is for you to proceed with cutting the RC,


On Thu, Aug 3, 2017 at 7:04 AM Jean-Baptiste Onofré <> wrote:

Another quick update. Regarding BEAM-2671, I asked help from Stas and
Aviem on
this one. It's our high priority as it's the main blocking issue before
cutting RC3.

At some point, if we are not able to move fast on this one, I would
propose to
cut RC3 as it is.


On 08/02/2017 08:52 PM, Jean-Baptiste Onofré wrote:

Thanks Eugene for the sumup.

BEAM-2708 is now fixed.

The last blocking issue for RC3 is BEAM-2671. I spent time today on this
investigating the different issues.

Agree that help from Aviem and Kenn would help for sure.

Aviem already started to kindly take a look on the Jira today.

Clearly, it would be great to fix BEAM-2671 in the coming 36 hours. I
would like
to submit RC3 to vote tomorrow or the day after (my time).

Thanks !

On 08/02/2017 08:24 PM, Eugene Kirpichov wrote:
We're down to 2 issues.

BEAM-2670 has been fixed. has a fix in review is the nasty one and we
don't understand it nor have a fix. Help is needed; some people who
help are +Kenn Knowles <> and +Aviem Zur <>

On Thu, Jul 27, 2017 at 6:41 AM Jean-Baptiste Onofré <>

Hi guys,

We have three open issues for the 2.1.0 that we need to fix before I
able to cut RC3:

I'm working on BEAM-2671.

Any help is welcome for the two other Jiras (BEAM-2587 and BEAM-2670).

Thanks !

On 07/18/2017 06:30 PM, Jean-Baptiste Onofré wrote:
Hi everyone,

Please review and vote on the release candidate #2 for the version
2.1.0, as

[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

The complete staging area is available for your review, which
* JIRA release notes [1],
* the official Apache source release to be deployed to
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.1.0-RC2" [5],
* website pull request listing the release and publishing the API
manual [6].
* Python artifacts are deployed along with the source release to the [2].

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




Jean-Baptiste Onofré
Talend -

Jean-Baptiste Onofré
Talend -

Jean-Baptiste Onofré
Talend -

Reply via email to