回复:[DISCUSS] Releasing Flink 1.4

2017-10-18 Thread Zhijiang(wangzhijiang999)
   Hi Stephan!    Thanks for replying.    I am clearly now, all the big new features would be covered in 1.5. And it is very necessary to fully test big changes before release.    Zhijiang --发件人:Stephan Ewen

回复:[DISCUSS] Releasing Flink 1.4

2017-10-18 Thread Zhijiang(wangzhijiang999)
Thanks for replying @Till Rohrmann , and I agree with your suggestion. Cheers,Zhijiang --发件人:Till Rohrmann 发送时间:2017年10月18日(星期三) 16:27收件人:dev ;

回复:[DISCUSS] Releasing Flink 1.4

2017-10-18 Thread Zhijiang(wangzhijiang999)
@Stephan Ewen , do you think the barrier alignment improvement should be covered in release-1.4 or release-1.5?It can avoid spilling data on receiver side for exactly-once and speed the barrier alignment. We have implemented this feature based on new credit-based flow control and verified the

Re: 回复:[DISCUSS] Releasing Flink 1.4

2017-10-13 Thread Bowen Li
+1. To give users a heads up, might be good to start to change the ‘target release’ of some Jira tickets from 1.4 to 1.5. Sent from my iPhone > On Oct 13, 2017, at 11:02 PM, Zhijiang(wangzhijiang999) > wrote: > > totally agree with the >

回复:[DISCUSS] Releasing Flink 1.4

2017-10-13 Thread Zhijiang(wangzhijiang999)
totally agree with the way.--发件人:Stephan Ewen 发送时间:2017年10月13日(星期五) 21:29收件人:dev@flink.apache.org 主 题:Re: [DISCUSS] Releasing Flink 1.4 I am in favor of doing this, if we can set it up in the