Re: TaskManager job lifecycle hooks

Could you speak to whether the lifecycle provided by RichFunction (open/close) would fit the requirement? https://ci.apache.org/projects/flink/flink-docs-release-1.3/api/java/org/apache/flink/api/common/functions/RichFunction.html#open-org.apache.flink.configuration.Configuration- On Thu, Dec 7,

Dataworks Summit EU call for abstracts

Dataworks Summit EU 2018 is in Berlin, April 16-19. The call for abstracts is open through December 15th. One of the tracks is IoT and Streaming, which is a great fit for Flink talks. https://dataworkssummit.com/abstracts/ Alan.

TaskManager job lifecycle hooks

Hey, I'm working on the Apache Beam portability story and trying to figure out how we can get the Flink runner to support the new portability API . In order to get the runner to work with portable SDKs, we need to be

Re: [VOTE] Release 1.4.0, release candidate #3

Just discovered: the removal of Flink's Future (FLINK-7252) causes a breaking change in connectors that use `org.apache.flink.runtime.checkpoint.MasterTriggerRestoreHook`, because `Future` is a type on one of the methods. To my knowledge, this affects only the Pravega connector. Curious to know

Re: [VOTE] Release 1.4.0, release candidate #3

I just noticed that I did a copy-and-paste error and the last paragraph about voting period should be this: The vote will be open for at least 72 hours. It is adopted by majority approval, with at least 3 PMC affirmative votes. Best, Aljoscha > On 7. Dec 2017, at 19:24, Bowen Li

[jira] [Created] (FLINK-8222) Update Scala version

Greg Hogan created FLINK-8222: - Summary: Update Scala version Key: FLINK-8222 URL: https://issues.apache.org/jira/browse/FLINK-8222 Project: Flink Issue Type: Improvement Components:

Re: [VOTE] Release 1.4.0, release candidate #3

I agree that it shouldn't block the release. The doc website part is even better! On Thu, Dec 7, 2017 at 1:09 AM, Aljoscha Krettek wrote: > Good catch, yes. This shouldn't block the release, though, since the doc > is always built form the latest state of a release branch,

[jira] [Created] (FLINK-8223) Update Hadoop versions

Greg Hogan created FLINK-8223: - Summary: Update Hadoop versions Key: FLINK-8223 URL: https://issues.apache.org/jira/browse/FLINK-8223 Project: Flink Issue Type: Improvement Components:

[jira] [Created] (FLINK-8221) Implement set of network latency benchmarks in Flink

Piotr Nowojski created FLINK-8221: - Summary: Implement set of network latency benchmarks in Flink Key: FLINK-8221 URL: https://issues.apache.org/jira/browse/FLINK-8221 Project: Flink Issue

[jira] [Created] (FLINK-8220) Define set of network throughput benchmarks in Flink

Piotr Nowojski created FLINK-8220: - Summary: Define set of network throughput benchmarks in Flink Key: FLINK-8220 URL: https://issues.apache.org/jira/browse/FLINK-8220 Project: Flink Issue

[jira] [Created] (FLINK-8219) Kinesis Connector metrics

Gary Oslon created FLINK-8219: - Summary: Kinesis Connector metrics Key: FLINK-8219 URL: https://issues.apache.org/jira/browse/FLINK-8219 Project: Flink Issue Type: Bug Components:

Re: [VOTE] Release 1.4.0, release candidate #3

Good catch, yes. This shouldn't block the release, though, since the doc is always built form the latest state of a release branch, i.e. the 1.4 doc on the website will update as soon as the doc on the release-1.4 branch is updated. > On 6. Dec 2017, at 20:47, Bowen Li