Re: [DISCUSS] Releasing Flink 1.5.0

A user reported a regression from 1.4.2. A batch job with a DeltaIteration gets stuck when being executed in a LocalEnvironment [1]. Cheers, Fabian [1] https://issues.apache.org/jira/browse/FLINK-9242 2018-04-23 21:09 GMT+02:00 Shuyi Chen : > Hi Aljoscha and Till, > > I've

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Aljoscha and Till, I've added 2 PRs to fix and harden the YARN kerberos security for flip-6. I think they should go in for 1.5.0 (particularly FLINK-8286 ). 1) https://github.com/apache/flink/pull/5896 (FLINK-8286

Re: [DISCUSS] Releasing Flink 1.5.0

Hi all, A small patch: https://github.com/apache/flink/pull/5789 (JIRA: https://issues.apache.org/jira/browse/FLINK-9103) was issued to help with SSL certificates in Kubernetes deployment where you don't control your IPs. As this is very small and helpful (at least to me and Edward who issued the

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Pavel, currently, it is extremely difficult to say when it will happen since Flink 1.5 includes some very big changes which need thorough testing. Depending on that and what else the community finds on the way, it may go faster or slower. Personally, I hope to finish the release until end of

Re: [DISCUSS] Releasing Flink 1.5.0

Approximately when is the release of Flink 1.5 planned? Best, 2018-03-01 11:20 GMT+02:00 Till Rohrmann : > Thanks for bringing this issue up Shashank. I think Aljoscha is taking a > look at the issue. It looks like a serious bug which we should definitely > fix. What I've

Re: [DISCUSS] Releasing Flink 1.5.0

Thanks for bringing this issue up Shashank. I think Aljoscha is taking a look at the issue. It looks like a serious bug which we should definitely fix. What I've heard so far is that it's not so trivial. Cheers, Till On Thu, Mar 1, 2018 at 9:56 AM, shashank734 wrote: >

Re: [DISCUSS] Releasing Flink 1.5.0

Can we have https://issues.apache.org/jira/browse/FLINK-7756 solved in this version. Cause unable to use checkpointing with CEP and RocksDB backend. -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/

Re: [DISCUSS] Releasing Flink 1.5.0

The release branch is now created [1]. Please be aware that we should only commit bug fixes to this branch henceforth. @Bowen, let's wait what Aljoscha says concerning FLINK-8667. If he agrees, then we can still merge it into the release branch. [1]

Re: [DISCUSS] Releasing Flink 1.5.0

+1 for cutting the release branch now. I'm also happy to volunteer as the release manager for Flink 1.5. Cheers, Till On Mon, Feb 26, 2018 at 3:45 PM, Aljoscha Krettek wrote: > End of last week was the day where we wanted to to the cut of the release > branch. There are

Re: [DISCUSS] Releasing Flink 1.5.0

End of last week was the day where we wanted to to the cut of the release branch. There are still a bunch of open blocker issues about bugs in our Jira: [1]. So I'm wondering whether we should actually cut the branch now because some commits would have to be merged on release-1.4, release-1.5,

Re: [DISCUSS] Releasing Flink 1.5.0

+1 from my side. Cheers, Till On Tue, Feb 13, 2018 at 9:52 AM, Piotr Nowojski wrote: > +0.95 from my side. > > Network changes are mostly reviewed and should be merged by the end of > this week. > > Piotrek > > > On 12 Feb 2018, at 17:41, Stephan Ewen

Re: [DISCUSS] Releasing Flink 1.5.0

+0.95 from my side. Network changes are mostly reviewed and should be merged by the end of this week. Piotrek > On 12 Feb 2018, at 17:41, Stephan Ewen wrote: > > I agree with the basic idea. I think there is no need to call it "soft > feature freeze" though - it is a

Re: [DISCUSS] Releasing Flink 1.5.0

I agree with the basic idea. I think there is no need to call it "soft feature freeze" though - it is a feature freeze (no new features get merged) ;-) What you are suggesting is to delay forking of the release-1.5 branch to avoid applying the bug fixes to too many branches. That makes sense. In

Re: [DISCUSS] Releasing Flink 1.5.0

For me as well +1. Cheers, Kostas > On Feb 12, 2018, at 2:59 PM, Timo Walther wrote: > > Sounds good to me. +1 from my side. > > Regards, > Timo > > > Am 2/12/18 um 2:56 PM schrieb Aljoscha Krettek: >> I agree with Chesnay: we should do a soft "feature freeze" first,

Re: [DISCUSS] Releasing Flink 1.5.0

Sounds good to me. +1 from my side. Regards, Timo Am 2/12/18 um 2:56 PM schrieb Aljoscha Krettek: I agree with Chesnay: we should do a soft "feature freeze" first, were we agree to not merge new features to master after that and then to the actual hard cutting of the release branch a while

Re: [DISCUSS] Releasing Flink 1.5.0

I agree with Chesnay: we should do a soft "feature freeze" first, were we agree to not merge new features to master after that and then to the actual hard cutting of the release branch a while later. For actual dates, I'm proposing end of this week (16.02.2018) as soft feature freeze and end

Re: [DISCUSS] Releasing Flink 1.5.0

Local state recovery is almost completely done. Only some reviews and merging of the final PRs is pending. The network stack improvements are on a good way to be finished by the end of this week or beginning of next week. To my knowledge we got recently green Travis builds :-) The network stack

Re: [DISCUSS] Releasing Flink 1.5.0

As Aljoscha said we wanted to do 1.5 soon after 1.4 based on the assumption that the 3 big features (FLIP-6, network stack changes, local state recovery) are nearly done. I'm unsure about local state recovery, but I still see open issues for FLIP-6 and the network stack rework. As such it

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Aljoscha, I believe that support for Broadcast State should also be in 1.5. There is an open PR https://github.com/apache/flink/pull/5230 for that and there are some pending issues related to scala api and documentation. Thanks, Kostas > On Feb 5,

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Shuyi, I will take a look at it again this week. I'm pretty sure it will be part of 1.5.0. Regards, Timo Am 2/5/18 um 5:25 PM schrieb Shuyi Chen: Hi Aljoscha, can we get this feature in for 1.5.0? We have a lot of internal users waiting for this feature. [FLINK-7923

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Aljoscha, can we get this feature in for 1.5.0? We have a lot of internal users waiting for this feature. [FLINK-7923 ] Support accessing subfields of a Composite element in an Object Array type column Thanks a lot Shuyi On Mon, Feb 5, 2018

Re: [DISCUSS] Releasing Flink 1.5.0

Hi guys, Sorry for jumping in, but I think [FLINK-8101] Elasticsearch 6.X support [FLINK-7386] Flink Elasticsearch 5 connector is not compatible with Elasticsearch 5.2+ client have long been awaited and there was one PR from me and from someone else showing the interest ;) So if you could

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Aljoscha, it would be great if we can include the first version of the SQL client (see FLIP-24, Implementation Plan 1). I will open a PR this week. I think we can merge this with explicit "experimental/alpha" status. It is far away from feature completeness but will be a great tool for

Re: [DISCUSS] Releasing Flink 1.5.0

Hi Aljoscha, Thanks for starting the discussion. I think there’s a few connector related must-have improvements that we should get in before the feature freeze, since quite a few users have been asking for them: [FLINK-6352] FlinkKafkaConsumer should support to use timestamp to set up start

[DISCUSS] Releasing Flink 1.5.0

Hi Everyone, When we decided to do the 1.4.0 release a while back we did that to get a stable release out before putting in a couple of new features. Back then, some of those new features (FLIP-6, network stack changes, local state recovery) were almost ready and we wanted to do a shortened