Re: Review Request 30078: Patch for KAFKA-1885

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30078/#review69534 --- Can you update the README.md document - Manikumar Reddy O On Jan.

Re: Review Request 30078: Patch for KAFKA-1885

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30078/#review69533 --- Ship it! Non-Binding +1 - Manikumar Reddy O On Jan. 24, 2015, 5:

Re: Review Request 30078: Patch for KAFKA-1885

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30078/#review69532 --- Ship it! Ship It! - Manikumar Reddy O On Jan. 24, 2015, 5:13 a.m

Re: Review Request 29755: Patch for KAFKA-1853

> On Jan. 24, 2015, 5:43 a.m., Jay Kreps wrote: > > core/src/main/scala/kafka/log/Log.scala, line 751 > > > > > > Seems like in the case of the exception we actually forcefully delete, > > but then after deleting sche

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290454#comment-14290454 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-24_11:21:07.patch > Unsuccessful suffix rename of expired LogSegment

Re: Review Request 29755: Patch for KAFKA-1853

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29755/ --- (Updated Jan. 24, 2015, 5:51 a.m.) Review request for kafka. Bugs: KAFKA-1853

Re: Review Request 29755: Patch for KAFKA-1853

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29755/#review69529 --- core/src/main/scala/kafka/log/Log.scala

[jira] [Commented] (KAFKA-1869) Openning some random ports while running kafka service

[ https://issues.apache.org/jira/browse/KAFKA-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290445#comment-14290445 ] jaikiran pai commented on KAFKA-1869: - [~huqian] As [~omkreddy] noted, that ephemeral

[jira] [Updated] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1853: Attachment: KAFKA-1853_2015-01-24_10:48:08.patch > Unsuccessful suffix rename of expired LogSegment

[jira] [Commented] (KAFKA-1853) Unsuccessful suffix rename of expired LogSegment can leak open files and also leave the LogSegment in an invalid state

[ https://issues.apache.org/jira/browse/KAFKA-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290442#comment-14290442 ] jaikiran pai commented on KAFKA-1853: - Updated reviewboard https://reviews.apache.org/

Re: Review Request 29755: Patch for KAFKA-1853

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29755/ --- (Updated Jan. 24, 2015, 5:18 a.m.) Review request for kafka. Bugs: KAFKA-1853

Re: Review Request 30078: Patch for KAFKA-1885

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30078/ --- (Updated Jan. 24, 2015, 5:13 a.m.) Review request for kafka. Bugs: KAFKA-1885

Re: [kafka-clients] Re: [VOTE] 0.8.2.0 Candidate 2 (with the correct links)

I don't think so--see if you buy my explanation. We previously defaulted to the byte array serializer and it was a source of unending frustration and confusion. Since it wasn't a required config people just went along plugging in whatever objects they had, and thinking that changing the parametric

[jira] [Updated] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jaikiran pai updated KAFKA-1885: Attachment: KAFKA-1885_2015-01-24_10:42:46.patch > Allow test methods in "core" to be individually r

[jira] [Commented] (KAFKA-1885) Allow test methods in "core" to be individually run from outside of the IDE

[ https://issues.apache.org/jira/browse/KAFKA-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290441#comment-14290441 ] jaikiran pai commented on KAFKA-1885: - Updated reviewboard https://reviews.apache.org/

Re: [kafka-clients] Re: [VOTE] 0.8.2.0 Candidate 2 (with the correct links)

Should value.serializer in the new java producer be defaulted to Array[Byte] ? I was working on testing some upgrade paths and got this ! return exception in callback when buffer cannot accept message ConfigException: Missing required configuration "value.serializer" which has no defau

[jira] [Commented] (KAFKA-1897) Enhance MockProducer for more sophisticated tests

[ https://issues.apache.org/jira/browse/KAFKA-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290436#comment-14290436 ] Jay Kreps commented on KAFKA-1897: -- Thanks for reporting this. It would be great to make

Cannot stop Kafka server if zookeeper is shutdown first

I was just playing around with the RC2 of 0.8.2 and noticed that if I shutdown zookeeper first I can't shutdown Kafka server at all since it goes into a never ending attempt to reconnect with zookeeper. I had to kill the Kafka process to stop it. I tried it against trunk too and there too I see

Re: [KIP-DISCUSSION] Mirror Maker Enhancement

QQ: If we ever use a different technique for the data channel selection than for the producer partitioning won't that break ordering? How can we ensure these things stay in sync? With respect to the new consumer--I really do want to encourage people to think through how MM will work with the new c

[jira] [Created] (KAFKA-1898) compatibility testing framework

Joe Stein created KAFKA-1898: Summary: compatibility testing framework Key: KAFKA-1898 URL: https://issues.apache.org/jira/browse/KAFKA-1898 Project: Kafka Issue Type: Bug Reporter:

Jenkins build is back to normal : Kafka-trunk #379

See

[jira] [Commented] (KAFKA-1461) Replica fetcher thread does not implement any back-off behavior

[ https://issues.apache.org/jira/browse/KAFKA-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290398#comment-14290398 ] Guozhang Wang commented on KAFKA-1461: -- [~sriharsha] Sorry for the late reply. This

[jira] [Updated] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1896: - Resolution: Fixed Status: Resolved (was: Patch Available) > Record size funcition of reco

[jira] [Commented] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290383#comment-14290383 ] Guozhang Wang commented on KAFKA-1896: -- Thanks for the patch, +1 and commit to trunk.

[jira] [Updated] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1896: - Fix Version/s: 0.8.3 > Record size funcition of record in mirror maker hit NPE when the message >

Re: Review Request 30231: Patch for KAFKA-1896

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30231/#review69525 --- Ship it! Ship It! - Guozhang Wang On Jan. 23, 2015, 10:30 p.m.,

[jira] [Created] (KAFKA-1897) Enhance MockProducer for more sophisticated tests

Navina Ramesh created KAFKA-1897: Summary: Enhance MockProducer for more sophisticated tests Key: KAFKA-1897 URL: https://issues.apache.org/jira/browse/KAFKA-1897 Project: Kafka Issue Type: B

Re: Review Request 30158: Patch for KAFKA-1835

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30158/#review69515 --- clients/src/main/java/org/apache/kafka/clients/producer/KafkaProduc

Re: [KIP-DISCUSSION] Mirror Maker Enhancement

I think that before we start making more changes to Mirror Maker there should be unit tests in place for it. Currently Mirror Maker is broker on trunk (there is a patch to fix it) because of a recent change. That is only going to get more unwieldily as more change happens. On Wed, Jan 21, 2015 at

[jira] [Updated] (KAFKA-1634) Improve semantics of timestamp in OffsetCommitRequests and update documentation

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-1634: - Attachment: KAFKA-1634_2015-01-23_16:06:07.patch > Improve semantics of timestamp in OffsetCommitR

Re: Review Request 27391: Fix KAFKA-1634

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27391/ --- (Updated Jan. 24, 2015, 12:06 a.m.) Review request for kafka. Bugs: KAFKA-163

[jira] [Commented] (KAFKA-1634) Improve semantics of timestamp in OffsetCommitRequests and update documentation

[ https://issues.apache.org/jira/browse/KAFKA-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290241#comment-14290241 ] Guozhang Wang commented on KAFKA-1634: -- Updated reviewboard https://reviews.apache.or

Re: [DISCUSS] KIP-5 - Broker Configuration Management

Cool. Yeah sorry to nag about these KIPs, and I hope it doesn't come across the wrong way. But the hope I really have for these is that they are complete enough that even highly involved users can see and understand the change, motivation, etc. I think that will do a ton to help extend the communit

Re: [VOTE] 0.8.2.0 Candidate 2 (with the correct links)

This is a reminder that the deadline for the vote is this Monday, Jan 26, 7pm PT. Thanks, Jun On Wed, Jan 21, 2015 at 8:28 AM, Jun Rao wrote: > This is the second candidate for release of Apache Kafka 0.8.2.0. There > has been some changes since the 0.8.2 beta release, especially in the new >

[jira] [Commented] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290132#comment-14290132 ] Jun Rao commented on KAFKA-1729: [~jjkoshy], thanks for the update. Yes, I agree that we d

[jira] [Updated] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1896: Status: Patch Available (was: Open) > Record size funcition of record in mirror maker hit NPE when

[jira] [Updated] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-1896: Attachment: KAFKA-1896.patch > Record size funcition of record in mirror maker hit NPE when the mess

[jira] [Commented] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

[ https://issues.apache.org/jira/browse/KAFKA-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290130#comment-14290130 ] Jiangjie Qin commented on KAFKA-1896: - Created reviewboard https://reviews.apache.org/

Review Request 30231: Patch for KAFKA-1896

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30231/ --- Review request for kafka. Bugs: KAFKA-1896 https://issues.apache.org/jira/b

[jira] [Created] (KAFKA-1896) Record size funcition of record in mirror maker hit NPE when the message value is null.

Jiangjie Qin created KAFKA-1896: --- Summary: Record size funcition of record in mirror maker hit NPE when the message value is null. Key: KAFKA-1896 URL: https://issues.apache.org/jira/browse/KAFKA-1896 P

[jira] [Commented] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290013#comment-14290013 ] Joel Koshy commented on KAFKA-1729: --- So perhaps it is best to leave the code as is since

[jira] [Commented] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290011#comment-14290011 ] Joel Koshy commented on KAFKA-1729: --- Ideally yes because it makes Java access unwieldy b

Re: Review Request 27799: New consumer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27799/ --- (Updated Jan. 23, 2015, 9:15 p.m.) Review request for kafka. Changes ---

Re: Review Request 27799: New consumer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27799/ --- (Updated Jan. 23, 2015, 9:13 p.m.) Review request for kafka. Bugs: KAFKA-1760

Re: Review Request 27799: New consumer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27799/ --- (Updated Jan. 23, 2015, 9:15 p.m.) Review request for kafka. Bugs: KAFKA-1760

Re: Review Request 27799: New consumer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27799/#review69453 --- core/src/test/scala/integration/kafka/api/ConsumerTest.scala

[jira] [Commented] (KAFKA-1760) Implement new consumer client

[ https://issues.apache.org/jira/browse/KAFKA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289987#comment-14289987 ] Jay Kreps commented on KAFKA-1760: -- Updated reviewboard https://reviews.apache.org/r/2779

[jira] [Updated] (KAFKA-1760) Implement new consumer client

[ https://issues.apache.org/jira/browse/KAFKA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1760: - Attachment: KAFKA-1760_2015-01-23_13:13:00.patch > Implement new consumer client > ---

Re: [DISCUSS] KIP-4 - Command line and centralized administrative operations

A centralized admin operation protocol would be very useful. One more general comment here is that controller is originally designed to only talk to other brokers through ControllerChannel, while the broker instance which carries the current controller is agnostic of its existence, and use KafkaAp

Re: Review Request 27799: New consumer

> On Jan. 22, 2015, 7:10 p.m., Guozhang Wang wrote: > > core/src/test/scala/integration/kafka/api/ConsumerTest.scala, line 64 > > > > > > Shall we add the @Test label just in case? > > Jay Kreps wrote: > No I don't

Re: Review Request 27799: New consumer

> On Jan. 23, 2015, 8:57 a.m., Ewen Cheslack-Postava wrote: > > clients/src/main/java/org/apache/kafka/clients/NetworkClient.java, line 247 > > > > > > I think these methods need to have timeouts on them. They get call

[jira] [Created] (KAFKA-1895) Investigate moving deserialization and decompression out of KafkaConsumer

Jay Kreps created KAFKA-1895: Summary: Investigate moving deserialization and decompression out of KafkaConsumer Key: KAFKA-1895 URL: https://issues.apache.org/jira/browse/KAFKA-1895 Project: Kafka

[jira] [Comment Edited] (KAFKA-1655) Allow high performance SimpleConsumer use cases to still work with new Kafka 0.9 consumer APIs

[ https://issues.apache.org/jira/browse/KAFKA-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289744#comment-14289744 ] Jay Kreps edited comment on KAFKA-1655 at 1/23/15 7:03 PM: --- I be

[jira] [Commented] (KAFKA-1655) Allow high performance SimpleConsumer use cases to still work with new Kafka 0.9 consumer APIs

[ https://issues.apache.org/jira/browse/KAFKA-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289744#comment-14289744 ] Jay Kreps commented on KAFKA-1655: -- I believe this is handled in the new consumer API. Ca

[jira] [Created] (KAFKA-1894) Avoid long or infinite blocking in the consumer

Jay Kreps created KAFKA-1894: Summary: Avoid long or infinite blocking in the consumer Key: KAFKA-1894 URL: https://issues.apache.org/jira/browse/KAFKA-1894 Project: Kafka Issue Type: Sub-task

Re: Review Request 29831: Patch for KAFKA-1476

> On Jan. 23, 2015, 4:47 p.m., Neha Narkhede wrote: > > core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala, line 259 > > > > > > => If set along with --delete > > > > I'm not sure if I fully understood

[jira] [Created] (KAFKA-1893) Allow regex subscriptions in the new consumer

Jay Kreps created KAFKA-1893: Summary: Allow regex subscriptions in the new consumer Key: KAFKA-1893 URL: https://issues.apache.org/jira/browse/KAFKA-1893 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-1892) System tests for the new consumer and co-ordinator

Jay Kreps created KAFKA-1892: Summary: System tests for the new consumer and co-ordinator Key: KAFKA-1892 URL: https://issues.apache.org/jira/browse/KAFKA-1892 Project: Kafka Issue Type: Sub-task

[jira] [Commented] (KAFKA-1332) Add functionality to the offsetsBeforeTime() API

[ https://issues.apache.org/jira/browse/KAFKA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289655#comment-14289655 ] Jay Kreps commented on KAFKA-1332: -- It will be good to rethink this API, but for now I th

[jira] [Resolved] (KAFKA-1331) Add ability to commit offsets to the new consumer

[ https://issues.apache.org/jira/browse/KAFKA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1331. -- Resolution: Duplicate Done as part of KAFKA-1760 > Add ability to commit offsets to the new consumer >

[jira] [Commented] (KAFKA-1862) Pass in the Time object into OffsetManager

[ https://issues.apache.org/jira/browse/KAFKA-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289649#comment-14289649 ] Aditya A Auradkar commented on KAFKA-1862: -- I can pick this up [~guozhang]. Can y

[jira] [Resolved] (KAFKA-1330) Implement subscribe(TopicPartition...partitions) and pool(timeout) in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps resolved KAFKA-1330. -- Resolution: Duplicate Done as part of KAFKA-1760 > Implement subscribe(TopicPartition...partitions) and

[jira] [Updated] (KAFKA-1329) Add metadata fetch and refresh functionality to the consumer

[ https://issues.apache.org/jira/browse/KAFKA-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jay Kreps updated KAFKA-1329: - Resolution: Fixed Status: Resolved (was: Patch Available) I incorporated this into KAFKA-1760. >

[jira] [Commented] (KAFKA-1729) add doc for Kafka-based offset management in 0.8.2

[ https://issues.apache.org/jira/browse/KAFKA-1729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289595#comment-14289595 ] Jun Rao commented on KAFKA-1729: Do you mean that you need to make code changes in the 0.8

Build failed in Jenkins: Kafka-trunk #378

See Changes: [neha.narkhede] KAFKA-1890 Fix bug preventing Mirror Maker from successful rebalance; reviewed by Gwen Shapira and Neha Narkhede -- [...truncated 502 lines...] kafka.log.LogTest > testAp

[jira] [Updated] (KAFKA-1890) Fix bug preventing Mirror Maker from successful rebalance.

[ https://issues.apache.org/jira/browse/KAFKA-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-1890: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks for the patch, Becket. P

Re: Review Request 30199: Patch for KAFKA-1890

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30199/#review69405 --- Ship it! Ship It! - Neha Narkhede On Jan. 23, 2015, 3:57 a.m., J

Re: Review Request 29831: Patch for KAFKA-1476

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29831/#review69400 --- core/src/main/scala/kafka/admin/ConsumerGroupCommand.scala

[jira] [Commented] (KAFKA-1646) Improve consumer read performance for Windows

[ https://issues.apache.org/jira/browse/KAFKA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289447#comment-14289447 ] Sriharsha Chintalapani commented on KAFKA-1646: --- [~jkreps] [~junrao] [~nehan

Re: [DISCUSS] KIPs

Wouldn't it make sense to move away from these rich binary broker descriptors ({ host, port, proto }) (which require protocol churning on change), and simply use URIs instead? E.g.: kafka://[:port]/ <-- cleantext proto on standard port 9092 kafkas://[:port] <-- SSL enveloped proto on s

[jira] [Comment Edited] (KAFKA-1786) implement a global configuration feature for brokers

[ https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262248#comment-14262248 ] Andrii Biletskyi edited comment on KAFKA-1786 at 1/23/15 12:05 PM: -

[jira] [Updated] (KAFKA-1786) implement a global configuration feature for brokers

[ https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Biletskyi updated KAFKA-1786: Attachment: KAFKA_1786.patch Patch KAFKA_1786.patch is based on KAFKA-1845 patch (KafkaConfi

Re: Review Request 27799: New consumer

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/27799/#review69355 --- clients/src/main/java/org/apache/kafka/clients/ClusterConnectionSta

[jira] [Updated] (KAFKA-1786) implement a global configuration feature for brokers

[ https://issues.apache.org/jira/browse/KAFKA-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrii Biletskyi updated KAFKA-1786: Attachment: (was: KAFKA-1786.patch) > implement a global configuration feature for broke

[jira] [Updated] (KAFKA-1476) Get a list of consumer groups

[ https://issues.apache.org/jira/browse/KAFKA-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Onur Karaman updated KAFKA-1476: Attachment: sample-kafka-consumer-groups-sh-output-1-23-2015.txt > Get a list of consumer groups > -

Re: Review Request 29831: Patch for KAFKA-1476

> On Jan. 23, 2015, 2:22 a.m., Neha Narkhede wrote: > > Onur, do you have an updated version of the console output from this tool? Hi Neha. I just uploaded it now. - Onur --- This is an automatically generated e-mail. To reply, visit: h