[
https://issues.apache.org/jira/browse/KAFKA-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665730#comment-13665730
]
Neha Narkhede commented on KAFKA-897:
-
+1. I think this looks good until we upgrade to
Do you mind filing a JIRA for this ? Feel free to upload a patch.
Thanks,
Neha
On Thu, May 23, 2013 at 12:25 PM, Chris Burroughs wrote:
> Did this ever get traction?
> https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=summary shows
> activity in the 0.7 branch but the last tag as
> kafka-0
Jason Weiss created KAFKA-918:
-
Summary: Change log.retention.hours to be log.retention.mins
Key: KAFKA-918
URL: https://issues.apache.org/jira/browse/KAFKA-918
Project: Kafka
Issue Type: New Fea
Did this ever get traction?
https://git-wip-us.apache.org/repos/asf?p=kafka.git;a=summary shows
activity in the 0.7 branch but the last tag as
kafka-0.7.2-incubating-candidate-5
http://mail-archives.apache.org/mod_mbox/kafka-dev/201302.mbox/%3cce36b916-a8b9-40c3-8a0e-958397c17...@gmail.com%3
Issue Subscription
Filter: outstanding kafka patches (77 issues)
The list of outstanding kafka patches
Subscriber: kafka-mailing-list
Key Summary
KAFKA-917 Expose zk.session.timeout.ms in console consumer
https://issues.apache.org/jira/browse/KAFKA-917
KAFKA-915 Sys
Swapnil Ghike created KAFKA-917:
---
Summary: Expose zk.session.timeout.ms in console consumer
Key: KAFKA-917
URL: https://issues.apache.org/jira/browse/KAFKA-917
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-917:
Attachment: kafka-917.patch
Attached a pathc.
> Expose zk.session.timeout.ms in con
Yes I believe the TopicErrorCode is also an int16. I will update the
documentation accordingly.
In general, if the protocol specification is not explicit it should be
made explicit. This will help other client driver authors in the future.
If you find any other errors or omissions in the documenta
Yes. You can see the details of the wire protocol here
https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-MetadataResponse
Thanks,
Neha
On May 23, 2013 9:43 AM, "Dave Peterson" wrote:
> Ok, thanks for the information. Looking at the wire for
Ok, thanks for the information. Looking at the wire format for the
metadata response, I see that the right hand side of the TopicMetadata
production contains a TopicErrorCode, and the right hand side of the
PartitionMetadata production contains a PartitionErrorCode. Are both
of these 16-bit value
[
https://issues.apache.org/jira/browse/KAFKA-916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665299#comment-13665299
]
Jun Rao commented on KAFKA-916:
---
Thanks for finding this. The deadlock is introduced because
[
https://issues.apache.org/jira/browse/KAFKA-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13665258#comment-13665258
]
Jun Rao commented on KAFKA-911:
---
If we just stop the replica to be shut down without sending
12 matches
Mail list logo