Re: [DISCUSS] Schedule and Scope for Flink 1.2

gt; >> > >> > > > >> > >> > > On Fri, Dec 16, 2016 at 5:23 PM, Aljoscha Krettek < > >> > >> aljos...@apache.org> > >> > >> > > wrote: > >> > >> > > > >> > >> > > > Hi, > >> > >&

Re: [DISCUSS] Schedule and Scope for Flink 1.2

t; > Hi, >> > >> > > > we're still working on making the backwards compatibility from >> 1.1 >> > >> > > > savepoints a reality. We have most of the code and some tests >> now >> > >> but >> > >> > it >> > >> > > > still needs some work. This is th

Re: [DISCUSS] Schedule and Scope for Flink 1.2

the > > >> > > > operators that we would like to make backwards compatible: > > >> > > > https://issues.apache.org/jira/browse/FLINK-5292 > > >> > > > > > >> > > > Cheers, > > >> > > > Aljoscha >

Re: [DISCUSS] Schedule and Scope for Flink 1.2

ljoscha > >> > > > > >> > > > On Tue, 13 Dec 2016 at 11:22 Feng Wang <feng.w...@outlook.com> > >> wrote: > >> > > > > >> > > > > It will be pretty good if 1.2 branch could be forked off within > >> this

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Cheers, >> > > > Aljoscha >> > > > >> > > > On Tue, 13 Dec 2016 at 11:22 Feng Wang <feng.w...@outlook.com> >> wrote: >> > > > >> > > > > It will be pretty good if 1.2 branch could be forked off within >>

Re: [DISCUSS] Schedule and Scope for Flink 1.2

ff within > this > > > > week, > > > > > and our guys working on FLIP-6 hope FLIP-6 branch could be merged > > into > > > > > master as soon as possible. > > > > > > > > > > Best Regards, &g

Re: [DISCUSS] Schedule and Scope for Flink 1.2

> into > > > > master as soon as possible. > > > > > > > > Best Regards, > > > > > > > > Feng Wang > > > > > > > > Alibaba > > > > > > > > > > > &

Re: [DISCUSS] Schedule and Scope for Flink 1.2

; > Feng Wang > > > > > > Alibaba > > > > > > ____ > > > From: Robert Metzger <rmetz...@apache.org> > > > Sent: Tuesday, December 13, 2016 4:58 AM > > > To: dev@flink.apache.org > > > Subject: Re: [DISCU

Re: [DISCUSS] Schedule and Scope for Flink 1.2

> > Feng Wang > > > > Alibaba > > > > > > From: Robert Metzger <rmetz...@apache.org> > > Sent: Tuesday, December 13, 2016 4:58 AM > > To: dev@flink.apache.org > > Subject: Re: [DISCUSS] Schedule and Scope for

Re: [DISCUSS] Schedule and Scope for Flink 1.2

oon as possible. > > Best Regards, > > Feng Wang > > Alibaba > > > From: Robert Metzger <rmetz...@apache.org> > Sent: Tuesday, December 13, 2016 4:58 AM > To: dev@flink.apache.org > Subject: Re: [DISCUSS] Schedule and Scope fo

Re: [DISCUSS] Schedule and Scope for Flink 1.2

We might also think about addressing: Relocate Flink's Hadoop dependency and its transitive dependencies (FLINK-5297), because a user reported that they cannot use the system due to a dependency issue. Cheers, Till On Thu, Dec 8, 2016 at 10:17 AM, Robert Metzger wrote: >

Re: [DISCUSS] Schedule and Scope for Flink 1.2

>>Secure Data Access (FLINK-3930) The PR for the work is still under review and I hope this could be included in the release. Regards, Vijay Sent from my iPhone > On Dec 6, 2016, at 11:51 AM, Robert Metzger wrote: > > UNRESOLVED Secure Data Access (FLINK-3930)

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Thank you all for your responses so far. The situation is better than I expected :) Let me summarize, and please object if you disagree: - RESOLVED dynamic Scaling / Key Groups (FLINK-3755) - RESOLVED Add Rescalable Non-Partitioned State (FLINK-4379) - RESOLVED [Split for 1.3] Add Flink 1.1

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hi Robert, I agree with Stefan on the estimation about 4. As for the testing, this can already start, as some basic operators have already been ported. Kostas > On Dec 6, 2016, at 5:50 PM, Stefan Richter > wrote: > > e already restored a job with general window

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Thanks Robert for reactivating the discussion. There are a few Table API related refactorings that I would like to have in 1.2 because they are API breaking: - FLINK-4704 Clean up the packages of the Table API and move it to the org.apache.flink.table package space. This is an API breaking change

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hi Robert, our pull request was closed in favor of https://github.com/apache/flink/pull/2861. However that PR still need some review I think (I also added some comment in the JIRA issue[1]). it will be great to have that fix in the next release :) [1]

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hi, I would like to reactivate this old email thread. The initial plan was to release 1.2 before Christmas, have RC1 by end of Nov / December and a feature freeze mid-November. Today (December 5), we did not yet do the feature freeze. I would like to get an overview again of the remaining

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hi to all, we've completed the PR #2790 to implement FLINK-4491 : we've added the comment that @zentol asked for a week ago and we also fixed a potential annoying problem we faced during indexing (if a

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hi to all, for the 1.2 release do you think it will be possible to include also a PR to implement FLINK-4491 ? The PR is waiting for a review at https://github.com/apache/flink/pull/2790. Best, Flavio On Fri, Oct 28, 2016 at 5:59 PM, Fabian

Re: [DISCUSS] Schedule and Scope for Flink 1.2

Hello, As Aljoshca said, the TriggerDSL depends on another PR, before it can be merged. In addition, this will change also the whole structure of how we test window/trigger related functionality, so some refactoring will be required. Kostas > On Oct 28, 2016, at 3:06 PM, Aljoscha Krettek

Re: [DISCUSS] Schedule and Scope for Flink 1.2

@Till: For the TriggerDSL we have to merge my open PR [1] for refactoring the WindowOperator/Trigger tests and then refactor the tests of the TriggerDSL to use the new test facilities introduced there. Plus then maybe some fixups. On Fri, 28 Oct 2016 at 11:17 Jark Wu

Re: [DISCUSS] Schedule and Scope for Flink 1.2

+1 to the schedule I hope to add 1) Table API: User defined table function (FLINK-4469 ) 2) Table API: Move Table API to org.apache.flink.table (FLINK-4704 ) The 1) has been discussed for a

Re: [DISCUSS] Schedule and Scope for Flink 1.2

+1 for the features to include. What is the state of the Trigger DSL? How much is left to be done before merging? Cheers, Till On Tue, Oct 25, 2016 at 4:32 PM, Aljoscha Krettek wrote: > +1 the schedule proposed so far. > > Do we also want to get in the "Trigger DSL" that

Re: [DISCUSS] Schedule and Scope for Flink 1.2

+1 the schedule proposed so far. Do we also want to get in the "Trigger DSL" that we've had brewing for a while now? On Mon, 17 Oct 2016 at 16:17 Stephan Ewen wrote: > I think this sounds very reasonable, +1 to the schedule. > > I would definitely add > - FLIP-10 (unify