Re: Restructuring Javadoc and Scaladoc for libraries

Hi Robert, Thanks for clarifying! I’ve filed this [1]. Regards, Chiwan Park [1]: https://issues.apache.org/jira/browse/FLINK-4223 > On Jul 14, 2016, at 9:56 PM, Robert Metzger wrote: > > Hi Chiwan, > > I think that's something we need to address. Probably the scaladoc plugin > is not configu

[jira] [Created] (FLINK-4223) Rearrange scaladoc and javadoc for Scala API

Chiwan Park created FLINK-4223: -- Summary: Rearrange scaladoc and javadoc for Scala API Key: FLINK-4223 URL: https://issues.apache.org/jira/browse/FLINK-4223 Project: Flink Issue Type: Improvemen

[jira] [Created] (FLINK-4222) Allow Kinesis configuration to get credentials from AWS Metadata

Nick Chadwick created FLINK-4222: Summary: Allow Kinesis configuration to get credentials from AWS Metadata Key: FLINK-4222 URL: https://issues.apache.org/jira/browse/FLINK-4222 Project: Flink

Re: Evaluating Apache Flink

Hi Kevin I think good series is "Introduction to Flink Streaming" from here: http://blog.madhukaraphatak.com/page2/ Perhaps add it to the list. Regards Jan On Fri, 2016-07-08 at 14:23 +0200, Kevin Jacobs wrote: > Hi, > > I am currently working working for an organization which is using > Apache  >

Re: In AbstractRocksDBState, why write a byte 42 between key and namespace?

I've faced a similar issue when serializing data two a key value store. Not sure how helpful it is for this case but two possible solutions I've used for persisting keys and values under different namespaces to the same key value store are: - have all namespaces be the same number of bytes and pre

Re: [DISCUSS] Move JIRA creation emails to separate list?

I can see how issue creations only can be too noisy for people who only check the dev list once in a while. If others feel like Theo, I don't have an issue with not-mirroring issue creation to the dev list. As a data point, in the past 30 days we have created 141 issues, which should have been mirr

Re: [DISCUSS] Commit tagging

It was intended as Till said... a list of preferred tags. On Fri, Jul 15, 2016 at 6:52 PM, Till Rohrmann wrote: > I agree with Robert that it would be a nice to have but not strictly > required. I think it would help to have a list of preferred tags so that > new community members have a place to

Re: [DISCUSS] Commit tagging

I agree with Robert that it would be a nice to have but not strictly required. I think it would help to have a list of preferred tags so that new community members have a place to look them up. Cheers, Till On Fri, Jul 15, 2016 at 11:41 AM, Robert Metzger wrote: > Hi Ufuk, > > I also saw these

Re: [DISCUSS] Move JIRA creation emails to separate list?

@Stephan, I'm not subscribed to issues@. The dev list itself includes JIRA creation emails (check out the archives ) @Aljoscha. It was mostly a concern for new users, who will get inundated with JIRA emails until they set up

Re: In AbstractRocksDBState, why write a byte 42 between key and namespace?

Every serializer should know how many bytes to consume. The key serializer should not need to look for 42 to know where to terminate. Otherwise this would be a problem case: key[42, 42] - 42 - namespace [42, 42, 42] key[42, 42, 42] - 42 - namespace [42, 42] On Fri, Jul 15, 2016 at 5:38 PM, Aljo

Re: [DISCUSS] FLIP-3 - Organization of Documentation

My take would be to take streaming as the common case and make special sections for batch. We can still have a few streaming-only sections (end to end exactly once) and a few batch-only sections (optimizer). On Fri, Jul 15, 2016 at 6:03 PM, Ufuk Celebi wrote: > I very much like this proposal. T

Re: Flink 1.1.0 Preview RC0

Most actually have a pending PR, except: https://issues.apache.org/jira/browse/FLINK-4207, https://issues.apache.org/jira/browse/FLINK-4201. I will assign FLINK-4201 to myself and hope to fix it over the weekend. The issue Stefan mentioned also has a pending PR by now. Hope to create the first RC

Re: [DISCUSS] FLIP-3 - Organization of Documentation

I very much like this proposal. This is long overdue. Our documentation never "broke up" with the old batch focus. That's where the current structure comes from and why people often don't find what they are looking for. We were trying to treat streaming and batch as equals. We never were "brave" en

Re: In AbstractRocksDBState, why write a byte 42 between key and namespace?

I left that in on purpose to protect against cases where the combination of key and namespace can be ambiguous. For example, these two combinations of key and namespace have the same written representation: key [0 1 2] namespace [3 4 5] (values in brackets are byte arrays) key [0 1] namespace [2 3

Re: [DISCUSS] Move JIRA creation emails to separate list?

Most of the JIRA noise should be on the "iss...@flink.apache.org" list. Make sure you are not subscribed there if you do not want that noise. On Fri, Jul 15, 2016 at 9:22 AM, Aljoscha Krettek wrote: > I'm afraid most people are ignoring this because they already have filters > set up and don'

Re: [DISCUSS] FLIP-1 : Fine grained recovery from task failures

I migrated the doc to the wiki On Fri, Jul 15, 2016 at 4:33 PM, Paris Carbone wrote: > +1 > > I like the proposal! > > Docs can work as supplementary medium to the wiki sometimes, in my view. > The wiki is definitely much preferred for tracking/archiving purposes but > it might not hurt if we so

Re: [DISCUSS] FLIP-1 : Fine grained recovery from task failures

+1 I like the proposal! Docs can work as supplementary medium to the wiki sometimes, in my view. The wiki is definitely much preferred for tracking/archiving purposes but it might not hurt if we sometimes also reference a doc with a somewhat evolving prototype there. > On 15 Jul 2016, at 15:

Re: In AbstractRocksDBState, why write a byte 42 between key and namespace?

My assumption is that this was a sanity check that actually just stuck in the code. It can probably be removed. PS: Moving this to the dev@flink.apache.org list... On Fri, Jul 15, 2016 at 11:05 AM, 刘彪 wrote: > In AbstractRocksDBState.writeKeyAndNamespace(): > > protected void writeKeyAndName

Re: Flink 1.1.0 Preview RC0

There are still 7 blockers for the release: https://issues.apache.org/jira/browse/FLINK-4207?jql=project%20%3D%20FLINK%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC most of them are assigned, some even have a pending pull request. On Thu, Jul 7, 2

[DISCUSS] FLIP-3 - Organization of Documentation

Hi all! I posted another FLIP - this time about a suggestion to make the documentation more accessible. FLIP-3 - Organization of Documentation https://cwiki.apache.org/confluence/display/FLINK/FLIP-3+-+Organization+of+Documentation The issue of accessibility of information came up repeatedly fro

Re: [DISCUSS] FLIP-1 : Fine grained recovery from task failures

So far the reactions were positive towards the proposal. If no one objects, I am going to assume lazy consensus and mark this FLIP as adopted. For the process, we'll post future FLIPs in the wiki directly, rather than in a Google Doc first. On Wed, Jul 13, 2016 at 5:17 PM, Aljoscha Krettek wrote

Re: [DISCUSS] Enhance Window Evictor in Flink

Hi all, How do we create a FLIP page, is there any permission setup required? I don't see any "Create" page(after logging in) option in the header as mentioned in https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals Thanks, Vishnu On Wed, Jul 13, 2016 at 10:22 PM, Vishn

[jira] [Created] (FLINK-4221) Show metrics in WebFrontend

Chesnay Schepler created FLINK-4221: --- Summary: Show metrics in WebFrontend Key: FLINK-4221 URL: https://issues.apache.org/jira/browse/FLINK-4221 Project: Flink Issue Type: Sub-task

Re: [DISCUSS] Commit tagging

Hi Ufuk, I also saw these inconsistencies in the tagging too, but I'm not sure if fixing this is worth the effort. As long as the tag somehow transports the intended message ("a change at the runtime "), its good enou

[jira] [Created] (FLINK-4220) ClientTest fails after port conflict

Ufuk Celebi created FLINK-4220: -- Summary: ClientTest fails after port conflict Key: FLINK-4220 URL: https://issues.apache.org/jira/browse/FLINK-4220 Project: Flink Issue Type: Bug Comp

[DISCUSS] Commit tagging

Hey devs, we currently tag commits with the JIRA issue and component(s), like: [FLINK-3943] [table] Add support for EXCEPT operator I was wondering whether it makes sense to write down a set of common commit tags for new contributors. The set of commit tags is quite unregulated right now and I

Re: [DISCUSS] Move JIRA creation emails to separate list?

I'm afraid most people are ignoring this because they already have filters set up and don't see it as a problem. If we now change the way the lists are set up this could potentially break the personal mail setup of some contributors. On Thu, 14 Jul 2016 at 19:56 Theodore Vasiloudis < theodoros.vas