[jira] [Commented] (KAFKA-622) Create mbeans per client

[ https://issues.apache.org/jira/browse/KAFKA-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499861#comment-13499861 ] Neha Narkhede commented on KAFKA-622: - 1. AbstractFetcherThread 1.1 Maybe the clientid

[jira] [Commented] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499860#comment-13499860 ] Jun Rao commented on KAFKA-532: --- Thanks for patch v5. Looks good. Just a couple of minor

[jira] [Commented] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499873#comment-13499873 ] Neha Narkhede commented on KAFKA-532: - Thanks for reviewing patch v5 quickly ! 50.

[jira] [Created] (KAFKA-625) Improve MessageAndMetadata to expose the partition

Neha Narkhede created KAFKA-625: --- Summary: Improve MessageAndMetadata to expose the partition Key: KAFKA-625 URL: https://issues.apache.org/jira/browse/KAFKA-625 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-616) Implement acks=0

[ https://issues.apache.org/jira/browse/KAFKA-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-616: Affects Version/s: 0.8 Implement acks=0 Key: KAFKA-616

[jira] [Resolved] (KAFKA-625) Improve MessageAndMetadata to expose the partition

[ https://issues.apache.org/jira/browse/KAFKA-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-625. - Resolution: Duplicate Fix Version/s: 0.8 Fixed as part of KAFKA-544

[jira] [Closed] (KAFKA-625) Improve MessageAndMetadata to expose the partition

[ https://issues.apache.org/jira/browse/KAFKA-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede closed KAFKA-625. --- Improve MessageAndMetadata to expose the partition

[jira] [Commented] (KAFKA-544) Retain key in producer and expose it in the consumer

[ https://issues.apache.org/jira/browse/KAFKA-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499938#comment-13499938 ] Neha Narkhede commented on KAFKA-544: - Minor comment - The API docs are broken in

[jira] [Updated] (KAFKA-133) Publish kafka jar to a public maven repository

[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede updated KAFKA-133: Affects Version/s: 0.8 Publish kafka jar to a public maven repository

[jira] [Commented] (KAFKA-133) Publish kafka jar to a public maven repository

[ https://issues.apache.org/jira/browse/KAFKA-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499940#comment-13499940 ] Neha Narkhede commented on KAFKA-133: - * How come this is not Fix Version 0.8? Should

[jira] [Commented] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499941#comment-13499941 ] Jun Rao commented on KAFKA-532: --- 50. My feeling is that request level error code conveys the

[jira] [Resolved] (KAFKA-532) Multiple controllers can co-exist during soft failures

[ https://issues.apache.org/jira/browse/KAFKA-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Neha Narkhede resolved KAFKA-532. - Resolution: Fixed 50. Agree that the request/response formats must be consistent. Let's bring

[jira] [Commented] (KAFKA-513) Add state change log to Kafka brokers

[ https://issues.apache.org/jira/browse/KAFKA-513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499949#comment-13499949 ] Neha Narkhede commented on KAFKA-513: - Swapnil, I think this JIRA is missing your

[jira] [Updated] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-612: -- Attachment: kafka-612-v2.patch Thanks for the review. Attach patch v2. 1.1 This is to handle the case that a

[jira] [Commented] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13499956#comment-13499956 ] Neha Narkhede commented on KAFKA-612: - Minor nitpick before you checkin v2 - Please

[jira] [Updated] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-612: -- Resolution: Fixed Fix Version/s: 0.8 Status: Resolved (was: Patch Available) Thanks for the

[jira] [Closed] (KAFKA-612) move shutting down of fetcher thread out of critical path

[ https://issues.apache.org/jira/browse/KAFKA-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao closed KAFKA-612. - move shutting down of fetcher thread out of critical path