+1 (binding)
Signature file on source looks good
Hash files on source look good
LICENSE file looks good
NOTICE file looks good
Source compiled
Tests passed
Standalone works
Test on YARN session works
- Henry
On Mon, Feb 8, 2016 at 9:37 AM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please
Hi Nick,
Thanks for bringing up the issue. I believe some people (including me) will
try to run Apache Flink on YARN =)
If more 0.10.x releases needed before 1.0 definitely would love to include
this in.
- Henry
On Tue, Feb 9, 2016 at 9:33 AM, Nick Dimiduk wrote:
> Agree it's not a blocker. I
Agree it's not a blocker. I can manage my own build with this patch if
necessary. Just thought I might not be the only one running streaming on
yarn.
On Tuesday, February 9, 2016, Henry Saputra wrote:
> Hi Ufuk,
>
> This is nice to have but not a blocker.
>
> So unless we find blocker for the cu
Hi Ufuk,
This is nice to have but not a blocker.
So unless we find blocker for the current RC I prefer to continue evaluate
and VOTE current RC.
- Henry
On Tuesday, February 9, 2016, Ufuk Celebi wrote:
> Hey Nick,
>
> I agree that this can be problematic when running multiple jobs on
> YARN.
+1 (binding)
Re-ran the tests from the previous RC with the new RC
- Built the code (Linux x64, Scala 2.10, Hadoop 2.3.0)
- Ran all tests
- Checked that there are no cross-version dependencies
- Checked that LICENSE and NOTICE are up to date
- Check planVisualizer util
- ran examples
Given the initial feedback, I would like to keep the RC going as well. The
upcoming 1.0 release will include the fix and if users complain about it for
0.10 we can do another release in the future.
—
+1 for this release.
Forwarding my tests from the last vote.
Additionally, I’ve verified that
I would also like to keep this RC. 0.10-SNAPSHOT will be equally stable.
On Tue, Feb 9, 2016 at 2:57 PM, Stephan Ewen wrote:
> I would be in favor of continuing the release candidate.
> The change is more a feature improvement than a bug, and these should come
> before release candidates (otherw
I would be in favor of continuing the release candidate.
The change is more a feature improvement than a bug, and these should come
before release candidates (otherwise we never get one done).
The 1.0 release is also very close, so this improvement will be available
anyways pretty soon.
I persona
Thanks Ufuk,
+1 for a new RC
2016-02-09 13:49 GMT+01:00 Ufuk Celebi :
> Hey Nick,
>
> I agree that this can be problematic when running multiple jobs on
> YARN. Since there is a chance that this might be the last release 0.10
> release, I would be OK to cancel the vote for your fix.
>
> Still, le
Hey Nick,
I agree that this can be problematic when running multiple jobs on
YARN. Since there is a chance that this might be the last release 0.10
release, I would be OK to cancel the vote for your fix.
Still, let's hear the opinion of others before doing this. What do you think?
– Ufuk
On Mo
Perhaps too late for the RC, but I've backported FLINK-3293 to this branch
via FLINK-3372. Would be nice for those wanting to monitory yarn
application submissions.
On Mon, Feb 8, 2016 at 9:37 AM, Ufuk Celebi wrote:
> Dear Flink community,
>
> Please vote on releasing the following candidate as
11 matches
Mail list logo
