[jira] [Created] (FLINK-7871) SlotPool should release its unused slot to RM

shuai.xu created FLINK-7871: --- Summary: SlotPool should release its unused slot to RM Key: FLINK-7871 URL: https://issues.apache.org/jira/browse/FLINK-7871 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-7870) SlotPool should cancel the slot request to RM if not need any more.

shuai.xu created FLINK-7870: --- Summary: SlotPool should cancel the slot request to RM if not need any more. Key: FLINK-7870 URL: https://issues.apache.org/jira/browse/FLINK-7870 Project: Flink

[jira] [Created] (FLINK-7869) Don't use PipelineErrorHandler on the client

Eron Wright created FLINK-7869: --- Summary: Don't use PipelineErrorHandler on the client Key: FLINK-7869 URL: https://issues.apache.org/jira/browse/FLINK-7869 Project: Flink Issue Type:

回复：[DISCUSS] Releasing Flink 1.4

   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

[jira] [Created] (FLINK-7868) Don't run checkstyle again for tests in Misc profile

Chesnay Schepler created FLINK-7868: --- Summary: Don't run checkstyle again for tests in Misc profile Key: FLINK-7868 URL: https://issues.apache.org/jira/browse/FLINK-7868 Project: Flink

Re: [DISCUSS] Releasing Flink 1.4

Hi Zhijiang! The proposal is to release 1.4 asap and have the master switch so 1.5 soon (early November or so). Merge the network code directly after that - the 1.5 release would come after flip-6, network stack, and local state caching is merged and tested. That gives us a better QA window.

[jira] [Created] (FLINK-7867) Start MetricQueryService on TaskManagerRunner

Till Rohrmann created FLINK-7867: Summary: Start MetricQueryService on TaskManagerRunner Key: FLINK-7867 URL: https://issues.apache.org/jira/browse/FLINK-7867 Project: Flink Issue Type:

Pattern change on runtime

Hi, I want to know, can we change the pattern on runtime? I've read on stackoverflow "at the moment flink does not support". Does it change?

Re: [DISCUSS] Releasing Flink 1.4

I went through the list of blocking issues and thinned it down to 25 open blockers and 12 in progress blockers. Please object if you don't agree with a specific issue. If not, then I suggest that we should concentrate on fixing these issues. Cheers, Till On Wed, Oct 18, 2017 at 10:54 AM, Stefan

[jira] [Created] (FLINK-7866) Weigh list of preferred locations for scheduling

Till Rohrmann created FLINK-7866: Summary: Weigh list of preferred locations for scheduling Key: FLINK-7866 URL: https://issues.apache.org/jira/browse/FLINK-7866 Project: Flink Issue Type:

回复：[DISCUSS] Releasing Flink 1.4

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

Re: [DISCUSS] Releasing Flink 1.4

Thanks for driving this effort Aljoscha. I would be in favour of quick feature freeze (31st of October). However, looking at the list of open and in progress blockers we still have 53 blocker issues. I think it is unrealistic to complete all of them within the next two weeks. I would therefore

回复：[DISCUSS] Releasing Flink 1.4

@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

[jira] [Created] (FLINK-7864) Support side-outputs in CoProcessFunction

Aljoscha Krettek created FLINK-7864: --- Summary: Support side-outputs in CoProcessFunction Key: FLINK-7864 URL: https://issues.apache.org/jira/browse/FLINK-7864 Project: Flink Issue Type: