Re: Flink-1.0.0 JobManager is not running in Docker Container on AWS

Hi Stephan & Ufuk, Thanks for your response. Yes there is a way in which you can run docker (net = host mode) in which guest machine's network stack gets shared by docker container. Unfortunately its not supported by AWS ECS. I do have one more question for you. Can you guys please explain me

[jira] [Created] (FLINK-3611) Wrong link in CONTRIBUTING.md

Martin Junghanns created FLINK-3611: --- Summary: Wrong link in CONTRIBUTING.md Key: FLINK-3611 URL: https://issues.apache.org/jira/browse/FLINK-3611 Project: Flink Issue Type: Bug

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

Hi, I think this is an important question that will surely come up in some cases in the future. I see your point Robert, that we have promised api compatibility for 1.x.y releases, but I am not sure that this should cover things that are clearly just unintended errors in the api from our side.

Re: Accessing the Configuration

Oh I see now thanks! -- View this message in context: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Accessing-the-Configuration-tp10696p10760.html Sent from the Apache Flink Mailing List archive. mailing list archive at Nabble.com.

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

On 13.03.2016 12:14, Robert Metzger wrote: I think its too early to fork off a 2.0 branch. I have absolutely no idea when a 2.0 release becomes relevant, could be easily a year from now. at first i was going to agree with Robert, but then...I mean the issue with not allowing breaking changes is

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

This approach means that we will have API breaking changes lingering around in random people's remote repos that will be untrackable in no time and people will not be able to build on each others changes. Whoever will have the pleasure to eventually merge those together will be on the receiving

Re: Accessing the Configuration

No, the RichFunction.open(Configuration) parameter is a feature from the DataSet API. Its for passing an operator-specific configuration through the ".withParameters(Configuration)" method. For more infos, just search for "withParameters" here:

Re: Accessing the Configuration

Isn't it what RichFunction.open(Configuration parameters) is for? -- View this message in context: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Accessing-the-Configuration-tp10696p10756.html Sent from the Apache Flink Mailing List archive. mailing list archive at Nabble.com.

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

I think its too early to fork off a 2.0 branch. I have absolutely no idea when a 2.0 release becomes relevant, could be easily a year from now. The API stability guarantees don't forbid adding new methods. Maybe we can find a good way to resolve the issue without changing the signature of

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

Ok, if that is what we promised let's stick to that. Then would you suggest to open a release-2.0 branch and merge it there? On Sun, Mar 13, 2016 at 11:43 AM, Robert Metzger wrote: > Hey, > JIRA was down for quite a while yesterday. Sadly, I don't think we can > merge the

Re: [streaming, scala] Scala DataStream#addSink returns Java DataStreamSink

Hey, JIRA was down for quite a while yesterday. Sadly, I don't think we can merge the change because its API breaking. One of the promises of the 1.0 release is that we are not breaking any APIs in the 1.x.y series of Flink. We can fix those issues with a 2.x release. On Sun, Mar 13, 2016 at 5:27