Re: [PROPOSAL] Splittable DoFn - Replacing the Source API with non-monolithic element processing in DoFn

Makes sense. Thanks Eugene. On Mon, Aug 8, 2016, 21:28 Eugene Kirpichov wrote: > Hi Amit, > > Glad you liked the proposal! Yes, adding the power to sequence reading of > sources against other things happening in the pipeline is one of the > biggest benefits. > > I

Re: [PROPOSAL] Website page or Jira to host all current proposal discussion and docs

+1 for a more formal "Improvement Proposals" with ids we can refer to: like Flink does too: https://cwiki.apache.org/confluence/display/FLINK/Flink+Improvement+Proposals On Mon, Aug 8, 2016 at 10:14 AM, Jean-Baptiste Onofré wrote: > Same think at Karaf:

Re: [PROPOSAL] Splittable DoFn - Replacing the Source API with non-monolithic element processing in DoFn

Jip, thanks, that answers it. On Fri, 5 Aug 2016 at 19:51 Eugene Kirpichov wrote: > Hi Aljoscha, > > AFAIK, the effect of .requiresDeduping() is that the runner inserts a > GBK/dedup transform on top of the read. This seems entirely compatible with > SDF, except it

Re: [PROPOSAL] Website page or Jira to host all current proposal discussion and docs

Same think at Karaf: https://cwiki.apache.org/confluence/display/KARAF/ Combine with Jira. Regards JB On 08/08/2016 10:03 AM, Aljoscha Krettek wrote: Please have a look at this: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals We recently started using this

Re: [PROPOSAL] Website page or Jira to host all current proposal discussion and docs

Please have a look at this: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals We recently started using this process in Flink and so far are quite happy with it. On Mon, 8 Aug 2016 at 06:52 Jean-Baptiste Onofré wrote: > Good point Ben. > > I would