[ANNOUCE] Apache Kafka 1.0.2 Released

2018-07-15 Thread Matthias J. Sax
The Apache Kafka community is pleased to announce the release for Apache Kafka 1.0.2. This is a bug fix release and it includes fixes and improvements from 27 JIRAs, including a few critical bugs. All of the changes in this release can be found in the release notes:

Re: [Discuss] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

2018-07-15 Thread Guozhang Wang
Hi Nishanth, Since even combining these two the scope is still relatively small I'd suggest just do it in one KIP if you're willing to work on them. If you do not then pleas feel free to create the JIRA for the second step so that others can pick it up. Guozhang On Sun, Jul 15, 2018 at 6:14

Re: KIP-327: Add describe all topics API to AdminClient

2018-07-15 Thread Colin McCabe
Thanks, Manikumar. I've been meaning to bring up KIP-142 again. It would definitely be a nice improvement. best, Colin On Sat, Jul 14, 2018, at 08:51, Manikumar wrote: > Hi Jason and Colin, > > Thanks for the feedback. I agree that having filtering support to the > Metadata API would be

Re: KIP-327: Add describe all topics API to AdminClient

2018-07-15 Thread Colin McCabe
Hi Stephane, Pagniation would be useful. But I think the more immediate need is to stop sending stuff over the wire that we don't even use. For example, imagine that you have a cluster with 50,000 topics and your Consumer subscribes to abracadabra*. Perhaps there's actually only 3 topics

Re: [DISCUSS] KIP-326: Schedulable KTable as Graph source

2018-07-15 Thread Matthias J. Sax
I think it would make a lot of sense to provide a simple DSL abstraction. Something like: KStream stream = ... KTable count = stream.count(); The missing groupBy() or grouByKey() class indicates a global counting operation. The JavaDocs should highlight the impact. One open question is, what

Re: [DISCUSS] KIP-328: Ability to suppress updates for KTables

2018-07-15 Thread Matthias J. Sax
Thanks for the update. I did a first pass over the updated KIP and think it makes sense. -Matthias On 7/11/18 5:47 PM, John Roesler wrote: > Hi all, > > I have updated KIP-328 with all the feedback I've gotten so far. Please > take another look and let me know what you think! > > Thanks, >

Re: [Discuss] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

2018-07-15 Thread Matthias J. Sax
There is no general protocol. We can include the changes in the current KIP or do a second KIP. If you don't want to include the change in this KIP, please create a new JIRA to track the other changes. You can assign the JIRA to yourself and start a second KIP if you want. You can also "link"

Re: [VOTE] 2.0.0 RC2

2018-07-15 Thread Satish Duggana
+1 (non-binding) - Ran testAll/releaseTarGzAll on 2.0.0-rc2 tag - Ran through quickstart of core/streams on builds generated from tag - Ran few internal apps targeting to topics on 3 node cluster. Thanks, Satish. On Sun 15 Jul, 2018, 9:55 PM Rajini Sivaram, wrote: > Hi Ismael, > > Thank you

Re: [Discuss] KIP-321: Add method to get TopicNameExtractor in TopologyDescription

2018-07-15 Thread Nishanth Pradeep
Thank you for the comments! I agree with these changes. So is the general protocol to update the same KIP, or is to scrap the current KIP and create a new one since it's beyond the scope of the original KIP? I am happy to do either. On Wed, Jul 4, 2018 at 1:48 PM Matthias J. Sax wrote: >

[jira] [Created] (KAFKA-7165) Error while creating ephemeral at /brokers/ids/BROKER_ID

2018-07-15 Thread Jonathan Santilli (JIRA)
Jonathan Santilli created KAFKA-7165: Summary: Error while creating ephemeral at /brokers/ids/BROKER_ID Key: KAFKA-7165 URL: https://issues.apache.org/jira/browse/KAFKA-7165 Project: Kafka

Re: [VOTE] 2.0.0 RC2

2018-07-15 Thread Rajini Sivaram
Hi Ismael, Thank you for pointing that out. I have re-uploaded the RC2 artifacts to maven including streams-scala_2.12. Also submitted a PR to update build & release scripts to include this. Thank you, Rajini On Fri, Jul 13, 2018 at 7:19 AM, Ismael Juma wrote: > Hi Rajini, > > Thanks for