[jira] [Created] (KAFKA-7630) Clarify that broker doesn't need scram username/password for delegation tokens

2018-11-14 Thread Andras Beni (JIRA)
Andras Beni created KAFKA-7630: -- Summary: Clarify that broker doesn't need scram username/password for delegation tokens Key: KAFKA-7630 URL: https://issues.apache.org/jira/browse/KAFKA-7630 Project: Kaf

Re: [KAFKA-7382] Guarantee atleast one replica of partition to be alive during topic creation

2018-11-14 Thread Suman B N
Any update on this? On Tue, Nov 13, 2018 at 1:17 PM Suman B N wrote: > Team, > > Review and merge - https://github.com/apache/kafka/pull/5822. > One round of review has been done by Mani Kumar Reddy in PR - > https://github.com/apache/kafka/pull/5665. > > -- > *Suman* > *OlaCabs* > -- *Suman*

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

2018-11-14 Thread Boyang Chen
Thank you for the clarification Jason! The proposals make sense here and let me continue the discussion. > Then the ids would be determined using some convention. Most likely, we would > just use sequential numbers 0, 1, 2, > etc. We do the same thing for partition ids. If we initialize a set

Re: [VOTE] KIP-354 Time-based log compaction policy

2018-11-14 Thread Matt Farmer
I'm a +1 (non-binding) — This looks like it would have saved us a lot of pain in an issue we had to debug recently. I can't go into details, but figuring out how to achieve this effect gave me quite a headache. :) On Mon, Nov 12, 2018 at 1:00 PM xiongqi wu wrote: > Hi all, > > Can I have one mor

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

2018-11-14 Thread Jason Gustafson
> > I feel this would make the current protocol harder to use. For example, on > KStream we typically would expect (number of instances * number of threads > per instance) consumers. Giving out all this many member names in a list > may not be easy, compared with dynamic generation of member names,

[jira] [Resolved] (KAFKA-7626) Possible duplicate message delivery with exactly-once semantics

2018-11-14 Thread Noam Berman (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noam Berman resolved KAFKA-7626. Resolution: Not A Problem > Possible duplicate message delivery with exactly-once semantics > -

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

2018-11-14 Thread Boyang Chen
Thanks Jason for the suggestions! I update the KIP with full schema changes. > we offer an admin API that lets a user define the expected members of the > group. I feel this would make the current protocol harder to use. For example, on KStream we typically would expect (number of instances * n

Re: [DISCUSS] KIP-388 Add observer interface to record request and response

2018-11-14 Thread Lincong Li
Hi Wesley, Thank you very much for your feedback. The concern on memory pressure is definitely valid. However it should be the user's job to keep this concern in mind and implement the observer in the most reasonable way for their use case. In other words, implement it at their own risks. The alt

[jira] [Created] (KAFKA-7629) Mirror maker goes into infinite loop

2018-11-14 Thread Darshan Mehta (JIRA)
Darshan Mehta created KAFKA-7629: Summary: Mirror maker goes into infinite loop Key: KAFKA-7629 URL: https://issues.apache.org/jira/browse/KAFKA-7629 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-7628) KafkaStream is not closing

2018-11-14 Thread Ozgur (JIRA)
Ozgur created KAFKA-7628: Summary: KafkaStream is not closing Key: KAFKA-7628 URL: https://issues.apache.org/jira/browse/KAFKA-7628 Project: Kafka Issue Type: Bug Components: streams Af

[jira] [Created] (KAFKA-7627) Kafka server on Windows crashes with misspelled case in topic name

2018-11-14 Thread Simon Rudchenko (JIRA)
Simon Rudchenko created KAFKA-7627: -- Summary: Kafka server on Windows crashes with misspelled case in topic name Key: KAFKA-7627 URL: https://issues.apache.org/jira/browse/KAFKA-7627 Project: Kafka

[jira] [Created] (KAFKA-7626) Possible duplicate message delivery with exactly-once semantics

2018-11-14 Thread Noam Berman (JIRA)
Noam Berman created KAFKA-7626: -- Summary: Possible duplicate message delivery with exactly-once semantics Key: KAFKA-7626 URL: https://issues.apache.org/jira/browse/KAFKA-7626 Project: Kafka Is

[jira] [Created] (KAFKA-7625) Kafka Broker node JVM crash - kafka.coordinator.transaction.TransactionCoordinator.$anonfun$handleEndTransaction

2018-11-14 Thread JIRA
Sebastian Puzoń created KAFKA-7625: -- Summary: Kafka Broker node JVM crash - kafka.coordinator.transaction.TransactionCoordinator.$anonfun$handleEndTransaction Key: KAFKA-7625 URL: https://issues.apache.org/jira/b

Re: Heads up: javac warnings are now treated as errors

2018-11-14 Thread Colin McCabe
Sounds good. Thanks for cleaning up the warnings! Colin On Mon, Nov 12, 2018, at 22:29, Ismael Juma wrote: > Hi all, > > As part of KAFKA-7612, all javac warnings were fixed or suppressed. To> > prevent them from reappearing, javac warnings are now treated as > errors. We> still have some scal

Re: [VOTE] KIP-374: Add '--help' option to all available Kafka CLI commands

2018-11-14 Thread Srinivas Reddy
Greetings, Code changes has been completed and pushed against to this PR. https://github.com/apache/kafka/pull/5910 Thank you. - Srinivas - Typed on tiny keys. pls ignore typos.{mobile app}

[jira] [Created] (KAFKA-7624) HOW TO FILETER NESTED THROUGH KAFKA CONNECT

2018-11-14 Thread Chenchu Lakshman kumar (JIRA)
Chenchu Lakshman kumar created KAFKA-7624: - Summary: HOW TO FILETER NESTED THROUGH KAFKA CONNECT Key: KAFKA-7624 URL: https://issues.apache.org/jira/browse/KAFKA-7624 Project: Kafka I

[jira] [Resolved] (KAFKA-7623) SMT STRUCT to MASK or FILTER

2018-11-14 Thread Chenchu Lakshman kumar (JIRA)
[ https://issues.apache.org/jira/browse/KAFKA-7623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chenchu Lakshman kumar resolved KAFKA-7623. --- Resolution: Fixed > SMT STRUCT to MASK or FILTER > --