[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0
[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao updated KAFKA-3343: --- Resolution: Fixed Status: Resolved (was: Patch Available) Issue resolved by pull request 1023 [https://github.com/apache/kafka/pull/1023] > GroupMetadataManager should use NoTimestamp for message v0 > -- > > Key: KAFKA-3343 > URL: https://issues.apache.org/jira/browse/KAFKA-3343 > Project: Kafka > Issue Type: Bug >Reporter: Jiangjie Qin >Assignee: Jiangjie Qin >Priority: Blocker > Fix For: 0.10.0.0 > > > When message version for __consumer_offsets is v0, the timestamp should be > NoTimestamp. Otherwise message instantiation will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0
[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3343: Status: Patch Available (was: Open) > GroupMetadataManager should use NoTimestamp for message v0 > -- > > Key: KAFKA-3343 > URL: https://issues.apache.org/jira/browse/KAFKA-3343 > Project: Kafka > Issue Type: Bug >Reporter: Jiangjie Qin >Assignee: Jiangjie Qin >Priority: Blocker > Fix For: 0.10.0.0 > > > When message version for __consumer_offsets is v0, the timestamp should be > NoTimestamp. Otherwise message instantiation will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0
[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3343: --- Priority: Blocker (was: Major) > GroupMetadataManager should use NoTimestamp for message v0 > -- > > Key: KAFKA-3343 > URL: https://issues.apache.org/jira/browse/KAFKA-3343 > Project: Kafka > Issue Type: Bug >Reporter: Jiangjie Qin >Assignee: Jiangjie Qin >Priority: Blocker > Fix For: 0.10.0.0 > > > When message version for __consumer_offsets is v0, the timestamp should be > NoTimestamp. Otherwise message instantiation will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0
[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3343: --- Reviewer: Jun Rao > GroupMetadataManager should use NoTimestamp for message v0 > -- > > Key: KAFKA-3343 > URL: https://issues.apache.org/jira/browse/KAFKA-3343 > Project: Kafka > Issue Type: Bug >Reporter: Jiangjie Qin >Assignee: Jiangjie Qin >Priority: Blocker > Fix For: 0.10.0.0 > > > When message version for __consumer_offsets is v0, the timestamp should be > NoTimestamp. Otherwise message instantiation will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KAFKA-3343) GroupMetadataManager should use NoTimestamp for message v0
[ https://issues.apache.org/jira/browse/KAFKA-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangjie Qin updated KAFKA-3343: Fix Version/s: 0.10.0.0 > GroupMetadataManager should use NoTimestamp for message v0 > -- > > Key: KAFKA-3343 > URL: https://issues.apache.org/jira/browse/KAFKA-3343 > Project: Kafka > Issue Type: Bug >Reporter: Jiangjie Qin >Assignee: Jiangjie Qin > Fix For: 0.10.0.0 > > > When message version for __consumer_offsets is v0, the timestamp should be > NoTimestamp. Otherwise message instantiation will fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
