Re: Dropping Java 7 support

Opened FLINK-7242 as an umbrella issue for this. On Wed, Jul 19, 2017 at 3:09 AM, Chesnay Schepler wrote: > Are the specific things we want to change right away? (build profiles > would be one thing) > > Would be neat to collect them in an umbrella issue. > > > On 18.07.2017

[jira] [Created] (FLINK-7242) Drop Java 7 Support

Eron Wright created FLINK-7242: --- Summary: Drop Java 7 Support Key: FLINK-7242 URL: https://issues.apache.org/jira/browse/FLINK-7242 Project: Flink Issue Type: Task Reporter: Eron

Flink savepoints - Confused

All: Based on flink 1.2 doc, savepoints are generated manually when running "flink savepoint jobId". But in my cluster I see 1000s of files in the form of e.g "savepoint-777cce9b". Who is creating these savepoints? -- View this message in context:

Re: [DISCUSS] Release 1.3.2 planning

FLINK-7211 is a trivial change for excluding the gelly examples javadoc from the release assembly and would be good to have fixed for 1.3.2. > On Jul 13, 2017, at 3:34 AM, Tzu-Li (Gordon) Tai wrote: > > I agree that FLINK-6951 should also be a blocker for 1.3.2. I’ll

[jira] [Created] (FLINK-7241) Fix YARN high availability documentation

Aljoscha Krettek created FLINK-7241: --- Summary: Fix YARN high availability documentation Key: FLINK-7241 URL: https://issues.apache.org/jira/browse/FLINK-7241 Project: Flink Issue Type: Bug

Re: is flink' states functionality futile?

Hi, State registered to Flink will be managed and checkpointed so that the state is fault-tolerant - records will update states with exactly-once guarantees even after restoring from job failures. In contrast, compare this to some normal field you have in your functions, that is updated per

is flink' states functionality futile?

Hi, After following all the instruction for how to manage a states with flink for non-keyed stream and after implementing all the required functions and defining all the variables (listState and the descriptor and so on), the program did actually worked well. But then I had to debug the program

Re: [VOTE] Release Apache Flink-shaded 1.0 (RC1)

Thanks a lot for preparing the release artifacts. While checking the source repo / release commit, I realized that you are not following the versioning scheme as flink: the current master has a "x.y-SNAPSHOT" version, and release candidates (and releases) get a x.y.z version. I wonder if it makes