Re: Towards Flink 0.10

One suggestion, going from 0.10 to 1.0 will be very confusing to people because at a cursory glance it can be easy to miss where the decimal point is. If you plan to go to 1.0 next you might number this release 0.99 or something. Alan. Maximilian Michels October 5,

Re: Towards Flink 0.10

Hey Alexey! I would like to get this in very soon, but I am not sure it will make it until the feature freeze fro 0.10. In that case, it should be coming up the next maintenance release after that... Greetings, Stephan On Tue, Oct 6, 2015 at 12:18 PM, Alexey Sapozhnikov

Re: Towards Flink 0.10

How about making a quick effort for this: https://issues.apache.org/jira/browse/FLINK-2313 It introduces an execution control handle (returned by StreamExecutionEnvironment.execute()) for operations like cancel(), getAccumulators(), scaleIn/Out(), ... It would be big time API breaking, so would

Re: Towards Flink 0.10

Hello everyone. Stephan, will 0.10 include the cache issues for createRemoteEnvironment? That not every addressing of environment will retransmit all the jars? On Tue, Oct 6, 2015 at 1:16 PM, Stephan Ewen wrote: > How about making a quick effort for this: >

Re: Towards Flink 0.10

@Stephan: There is an issue for implementing a detached job submission: https://issues.apache.org/jira/browse/FLINK-2797. That has the advantage that the execution mode and control flow is not hard-coded in the user job. I think it makes more sense to integrate methods like

Re: Towards Flink 0.10

Thanks Greg, we have added that to the list of API breaking changes. On Mon, Oct 5, 2015 at 4:36 PM, Greg Hogan wrote: > Max, > > Stephan noted that FLINK-2723 is an API breaking change. The CopyableValue > interface has a new method "T copy()". Commit >

Re: Towards Flink 0.10

Max, Stephan noted that FLINK-2723 is an API breaking change. The CopyableValue interface has a new method "T copy()". Commit e727355e42bd0ad7d403aee703aaf33a68a839d2 Greg On Mon, Oct 5, 2015 at 10:20 AM, Maximilian Michels wrote: > Hi Flinksters, > > After a lot of

Towards Flink 0.10

Hi Flinksters, After a lot of development effort in the past months, it is about time to move towards the next major release. We decided to move towards 0.10 instead of a milestone release. This release will probably be the last release before 1.0. For 0.10 we most noticeably have the new

Re: Towards Flink 0.10

Yes, FLINK-2785 that's right! Alright, thanks a lot! On 5 October 2015 at 18:31, Fabian Hueske wrote: > Hi Vasia, > > I guess you are referring to FLINK-2785. Should be fine, as there is a PR > already. > I'll add it to the list. > > Would be nice if you could take care of

Re: Towards Flink 0.10

Thanks Max. I extended the list of issues to fix for the release. 2015-10-05 17:10 GMT+02:00 Maximilian Michels : > Thanks Greg, we have added that to the list of API breaking changes. > > On Mon, Oct 5, 2015 at 4:36 PM, Greg Hogan wrote: > > > Max, > > > >

Re: Towards Flink 0.10

Thank you Max for putting the list together and to whomever added FLINK-2561 to the list :) I would also add FLINK-2561 (pending PR #1205). It's a sub-task of FLINK-2561, so maybe it's covered as is. If we go for Gelly graduation, I can take care of FLINK-2786 "Remove Spargel from source code and

Re: Towards Flink 0.10

Hi Vasia, I guess you are referring to FLINK-2785. Should be fine, as there is a PR already. I'll add it to the list. Would be nice if you could take care of FLINK-2786 (remove Spargel). Cheers, Fabian 2015-10-05 18:25 GMT+02:00 Vasiliki Kalavri : > Thank you Max