[jira] [Work started] (KAFKA-3025) KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and Producer/ConsumerRecord

[ https://issues.apache.org/jira/browse/KAFKA-3025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on KAFKA-3025 started by Jiangjie Qin. --- > KIP-31&KIP-32 (part 1): Add timestamp field to message, configs, and > Producer/

[jira] [Created] (KAFKA-3036) Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker.

Jiangjie Qin created KAFKA-3036: --- Summary: Add up-conversion and down-conversion of ProducerRequest and FetchRequest to broker. Key: KAFKA-3036 URL: https://issues.apache.org/jira/browse/KAFKA-3036 Proj

[jira] [Created] (KAFKA-3037) Number of alive brokers not known after single node cluster startup

Stevo Slavic created KAFKA-3037: --- Summary: Number of alive brokers not known after single node cluster startup Key: KAFKA-3037 URL: https://issues.apache.org/jira/browse/KAFKA-3037 Project: Kafka

[jira] [Created] (KAFKA-3038) Speeding up partition reassignment after broker failure

Eno Thereska created KAFKA-3038: --- Summary: Speeding up partition reassignment after broker failure Key: KAFKA-3038 URL: https://issues.apache.org/jira/browse/KAFKA-3038 Project: Kafka Issue Typ

Re: [VOTE] KIP-32 Add CreateTime and LogAppendTime to Kafka message.

Thanks Becket, Anne and Neha for responding to my concern. I had an offline discussion with Anne where she helped me understand the migration process. It isn't as bad as it looks in the KIP :) If I understand it correctly, the process (for users) will be: 1. Prepare for upgrade (set format.versi

[jira] [Updated] (KAFKA-2105) NullPointerException in client on MetadataRequest

[ https://issues.apache.org/jira/browse/KAFKA-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2105: - Reviewer: Gwen Shapira (was: Jun Rao) > NullPointerException in client on MetadataRequest > -

[jira] [Updated] (KAFKA-2358) Cluster collection returning methods should never return null

[ https://issues.apache.org/jira/browse/KAFKA-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-2358: - Reviewer: Jason Gustafson Assigning to [~hachikuji] to review and check if it is already fixed in

[jira] [Created] (KAFKA-3039) Temporary loss of leader resulted in log being completely truncated

Imran Patel created KAFKA-3039: -- Summary: Temporary loss of leader resulted in log being completely truncated Key: KAFKA-3039 URL: https://issues.apache.org/jira/browse/KAFKA-3039 Project: Kafka

Re: [VOTE] KIP-32 Add CreateTime and LogAppendTime to Kafka message.

Becket, Please let us know once you have updated the wiki page regarding the migration plan. Thanks! Guozhang On Wed, Dec 23, 2015 at 11:52 AM, Gwen Shapira wrote: > Thanks Becket, Anne and Neha for responding to my concern. > > I had an offline discussion with Anne where she helped me underst

Re: [VOTE] KIP-32 Add CreateTime and LogAppendTime to Kafka message.

Also I agree with Gwen that such changes may worth a 0.10 release or even 1.0, having it in 0.9.1 would be quite confusing to users. Guozhang On Wed, Dec 23, 2015 at 1:36 PM, Guozhang Wang wrote: > Becket, > > Please let us know once you have updated the wiki page regarding the > migration plan

[jira] [Commented] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070294#comment-15070294 ] Mayuresh Gharat commented on KAFKA-2937: [~rsivaram] This can occur if during dele

[jira] [Commented] (KAFKA-3011) Consumer.poll(0) blocks if Kafka not accessible

[ https://issues.apache.org/jira/browse/KAFKA-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070305#comment-15070305 ] Ewen Cheslack-Postava commented on KAFKA-3011: -- [~ebowman] I think this is a

[jira] [Comment Edited] (KAFKA-2937) Topics marked for delete in Zookeeper may become undeletable

[ https://issues.apache.org/jira/browse/KAFKA-2937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070294#comment-15070294 ] Mayuresh Gharat edited comment on KAFKA-2937 at 12/23/15 11:21 PM: -

Re: Consider increasing the default reserved.broker.max.id

Which other numbering schemes do we want to be able to un-break by increasing this default? For example, I know some people use the IP address with dots removed -- we'd have to use a very large # to make sure that worked. Before making another change, it'd be good to know what other schemes people

[jira] [Commented] (KAFKA-3006) Make collection default container type for sequences in the consumer API

[ https://issues.apache.org/jira/browse/KAFKA-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070331#comment-15070331 ] Ewen Cheslack-Postava commented on KAFKA-3006: -- So, now I'm not sure what con

The JIRA Awakens [KAFKA-1841]

Hi all, I've been helping debug an issue filed against kafka-python related to compatibility w/ Hortonworks 2.3.0.0 kafka release. As I understand it, HDP is currently based on snapshots of apache/kafka trunk, merged with some custom patches from HDP itself. In this case, HDP's 2.3.0.0 kafka rele

[jira] [Created] (KAFKA-3040) Broker didn't report new data after change in leader

Imran Patel created KAFKA-3040: -- Summary: Broker didn't report new data after change in leader Key: KAFKA-3040 URL: https://issues.apache.org/jira/browse/KAFKA-3040 Project: Kafka Issue Type: Bu

[GitHub] kafka pull request: KAFKA-3002: Make available to specify hostname...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/685 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabl

[jira] [Commented] (KAFKA-3002) Make available to specify hostname with Uppercase at broker list

[ https://issues.apache.org/jira/browse/KAFKA-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070585#comment-15070585 ] ASF GitHub Bot commented on KAFKA-3002: --- Github user asfgit closed the pull request

[jira] [Resolved] (KAFKA-3002) Make available to specify hostname with Uppercase at broker list

[ https://issues.apache.org/jira/browse/KAFKA-3002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-3002. -- Resolution: Fixed Fix Version/s: 0.9.1.0 Issue resolved by pull request 6

Build failed in Jenkins: kafka-trunk-jdk8 #256

See Changes: [me] KAFKA-3002; Allow uppercase letters in hostnames -- [...truncated 1410 lines...] kafka.log.LogTest > testTimeBasedLogRollJitter PASSED kafka.log.LogTest > testParseTopicPartiti

Jenkins build is back to normal : kafka_0.9.0_jdk7 #76

See

Re: [kafka-clients] The JIRA Awakens [KAFKA-1841]

Dana, Not sure about the old merge script, but with the new one used for GitHub PRs it tracks the branches you choose to commit to and can update the JIRA automatically, tagging the appropriate fix versions. So from now on, the appropriate JIRA queries for issues with, e.g., fix version 0.9.0.1 bu

[jira] [Commented] (KAFKA-3039) Temporary loss of leader resulted in log being completely truncated

[ https://issues.apache.org/jira/browse/KAFKA-3039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070701#comment-15070701 ] James Cheng commented on KAFKA-3039: Sounds related to https://issues.apache.org/jira/

[jira] [Created] (KAFKA-3041) NullPointerException in new Consumer API on broker restart

Enrico Olivelli created KAFKA-3041: -- Summary: NullPointerException in new Consumer API on broker restart Key: KAFKA-3041 URL: https://issues.apache.org/jira/browse/KAFKA-3041 Project: Kafka