Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-15 Thread Robert Metzger
I'll now kick off the RC creation process. On Sun, May 14, 2017 at 7:14 PM, Stephan Ewen wrote: > +1 for another RC once the shading fix is merged. > > Even if RC1 would have pending issues, users that want to help testing need > a new RC, because (as Robert said), RC0's shading issues make it v

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-14 Thread Stephan Ewen
+1 for another RC once the shading fix is merged. Even if RC1 would have pending issues, users that want to help testing need a new RC, because (as Robert said), RC0's shading issues make it virtually unusable... On Fri, May 12, 2017 at 3:45 PM, Robert Metzger wrote: > I'm considering to do ano

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-12 Thread Robert Metzger
I'm considering to do another non voting RC1 on Monday with the incremental checkpointing and maven fixes in (and of course as many other things as possible). Once the other critical fixes are in (ideally Tuesday or Wednesday), I'll create the first voting one. The current RC0 is almost unusable b

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-12 Thread Greg Hogan
+1 for sticking to the code freeze deadline and building a new release candidate but since the release is still two weeks off (5/26) I think it better to delay voting to give time for additional bug fixes. > On May 11, 2017, at 10:19 AM, Robert Metzger wrote: > > It seems that we found quite

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-12 Thread Till Rohrmann
I would like to get https://issues.apache.org/jira/browse/FLINK-6020 also in the 1.3.0 release, because multiple job submissions to the same cluster can corrupt the stored blobs. Cheers, Till On Fri, May 12, 2017 at 9:52 AM, Fabian Hueske wrote: > Hi Haohui, > > open issue for 1.3 are tracked i

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-12 Thread Fabian Hueske
Hi Haohui, open issue for 1.3 are tracked in JIRA. You can specify "Fix version: 1.3.0" and an appropriate priority. I updated a couple of issues to have the fix version tag. Any bug that is found while release testing should be added to this list by setting fix version, priority, and component.

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Haohui Mai
Hi, Just curious -- do we have anything to track the blockers on the table / SQL side? For example, it seems to me that FLINK-6563 is a blocker because all group windows in SQL will not work without it. I think that Fabian / Timo might want to get several jiras into 1.3. Regards, Haohui On Thu,

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Stephan Ewen
>From the above list, I addressed a bunch of issues. - FLINK-6514 Cannot start Flink Cluster in standalone mode has an open Pull Request: - master: https://github.com/apache/flink/pull/3876 - 1.3: https://github.com/apache/flink/pull/3877 Left are: - FLINK-6537 Umbrella issue for fixes to

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Robert Metzger
It seems that we found quite a large number of critical issues in the first RC. - FLINK-6537 Umbrella issue for fixes to incremental snapshots (Stefan has a PR open to fix the critical ones) - FLINK-6531 Deserialize checkpoint hooks with user classloader (has a pending PR) - FLINK-6515 KafkaConsum

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Till Rohrmann
Unfortunately, it won't be fully functional in 1.3. Cheers, Till On Thu, May 11, 2017 at 10:45 AM, Renjie Liu wrote: > @Rohrmann Will FLIP 6 be fully functional in 1.3 release? > > On Thu, May 11, 2017 at 4:12 PM Gyula Fóra wrote: > > > Thanks Stefan! > > Gyula > > > > Stefan Richter ezt írta

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Renjie Liu
@Rohrmann Will FLIP 6 be fully functional in 1.3 release? On Thu, May 11, 2017 at 4:12 PM Gyula Fóra wrote: > Thanks Stefan! > Gyula > > Stefan Richter ezt írta (időpont: 2017. máj. > 11., Cs, 10:04): > > > > > Hi, > > > > Thanks for reporting this. I found a couple of issues yesterday and I am

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Gyula Fóra
Thanks Stefan! Gyula Stefan Richter ezt írta (időpont: 2017. máj. 11., Cs, 10:04): > > Hi, > > Thanks for reporting this. I found a couple of issues yesterday and I am > currently working on a bundle of fixes. I will take a look at this problem, > and if it is already covered. > > Best, > Stefan

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Stefan Richter
Hi, Thanks for reporting this. I found a couple of issues yesterday and I am currently working on a bundle of fixes. I will take a look at this problem, and if it is already covered. Best, Stefan > Am 11.05.2017 um 09:47 schrieb Gyula Fóra : > > Hi, > I am not sure if this belong to this thr

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Gyula Fóra
Hi, I am not sure if this belong to this thread, but while trying to run a job with rocks incremental backend I ran into 2 issues: One with savepoints, I can't figure out because I can't make sense of the error or how it happenned: The error stack trace is here: https://gist.github.com/gyfora/2f7b

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-11 Thread Till Rohrmann
Hi Renjie, 1.3 already contains some Flip-6 code. However, it is not yet fully functional. What you already can do is to run local jobs on the Flip-6 code base by instantiating a MiniCluster and then using the Flip6LocalStreamEnvironment. Cheers, Till On Thu, May 11, 2017 at 6:00 AM, Renjie Liu

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-10 Thread Renjie Liu
Hi, all: Will the FLIP 6 be included in release 1.3? On Wed, May 10, 2017 at 9:48 PM Gyula Fóra wrote: > Thanks you! :) > > Chesnay Schepler ezt írta (időpont: 2017. máj. 10., > Sze, 15:44): > > > I guess it is related to this one > > https://issues.apache.org/jira/browse/FLINK-6514 ? > > > > O

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-10 Thread Gyula Fóra
Thanks you! :) Chesnay Schepler ezt írta (időpont: 2017. máj. 10., Sze, 15:44): > I guess it is related to this one > https://issues.apache.org/jira/browse/FLINK-6514 ? > > On 10.05.2017 15:34, Gyula Fóra wrote: > > Hi, > > > > I tried to run an application on 1.3 but I keep getting the followin

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-10 Thread Chesnay Schepler
I guess it is related to this one https://issues.apache.org/jira/browse/FLINK-6514 ? On 10.05.2017 15:34, Gyula Fóra wrote: Hi, I tried to run an application on 1.3 but I keep getting the following error: java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.security.Use

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-10 Thread Gyula Fóra
Hi, I tried to run an application on 1.3 but I keep getting the following error: java.lang.NoClassDefFoundError: Could not initialize class org.apache.hadoop.security.UserGroupInformation at org.apache.flink.runtime.security.modules.HadoopModule.install(HadoopModule.java:45) at org.apache.flink.ru

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Chesnay Schepler
I looked into AppVeyor and managed to create a working setup that replicates the problems i encounter locally. https://ci.appveyor.com/project/zentol/flink/build/1.0.12 The integration should be as simple as placing an appveyor.yml (similar to the travis.yml) into the repository and asking INFR

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Robert Metzger
Chesnay, I would propose to look into a CI solution for Windows. I'll try out appveyor.com for my Flink fork and report back how well it works (let me know if you want to look into it). On Tue, May 9, 2017 at 10:05 AM, Stephan Ewen wrote: > @Renjie What functionality are you looking for? Most st

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Renjie Liu
I'm just looking forward basic functionalities, e.g. a single web port for all flink jobs. On Tue, May 9, 2017 at 4:05 PM Stephan Ewen wrote: > @Renjie What functionality are you looking for? Most stuff should work in > the normal master branch. > > > On Tue, May 9, 2017 at 10:02 AM, Renjie Liu

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Stephan Ewen
@Renjie What functionality are you looking for? Most stuff should work in the normal master branch. On Tue, May 9, 2017 at 10:02 AM, Renjie Liu wrote: > Stephan: > This means that we can use FLIP 6 for basic functionality now? Any > document for setting up that? Will FLIP 6 be finished in rele

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Renjie Liu
Stephan: This means that we can use FLIP 6 for basic functionality now? Any document for setting up that? Will FLIP 6 be finished in release 1.3? On Tue, May 9, 2017 at 3:43 PM Stephan Ewen wrote: > @Renjie Liu: A good part of the FLIP-6 code is in there, but not all. > > It does run well on Ya

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Chesnay Schepler
This RC (and 1.4-SNAPSHOT for that matter) cannot be compiled on Windows due to the rat-plugin not detecting certain test savepoints as binary files. The files in question are the "savepoints" created by the StreamOperatorTestHarness. This is not a new problem and has happened before, but we n

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-09 Thread Stephan Ewen
@Renjie Liu: A good part of the FLIP-6 code is in there, but not all. It does run well on Yarn, Mesos, Docker, etc. We need to finish the FLIP-6 work mainly for full elasticity. On Tue, May 9, 2017 at 5:24 AM, Renjie Liu wrote: > Hi, does this include the FLIP6? > > On Tue, May 9, 2017 at 2:2

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-08 Thread Renjie Liu
Hi, does this include the FLIP6? On Tue, May 9, 2017 at 2:29 AM Stephan Ewen wrote: > Did a quick test: Simply adding the > "org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer" > helps with NOTICE files, > but does not add the required BSD licence copies. > > > On Mon, May 8

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-08 Thread Stephan Ewen
Did a quick test: Simply adding the "org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer" helps with NOTICE files, but does not add the required BSD licence copies. On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen wrote: > I did the first pass for the legal check. > > - Source

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-08 Thread Stephan Ewen
I did the first pass for the legal check. - Source LICENSE and NOTICE are okay - In the shaded JAR files, we are not bundling the license and notice files of the dependencies we include in the shaded jars. => Not a problem for Guava (Apache Licensed) => I think is a problem for ASM

[DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

2017-05-08 Thread Robert Metzger
Hi Devs, I've created a first non-voting release candidate for Flink 1.3.0. Please use this RC to test as much as you can and provide feedback to the Flink community. The more we find and fix now, the better Flink 1.3.0 wil be :) I've CC'ed the user@ mailing list to get more people to test it. DO