[jira] [Commented] (KAFKA-3907) Better support for user-specific committing in the Streams DSL

[ https://issues.apache.org/jira/browse/KAFKA-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285541#comment-16285541 ] Guozhang Wang commented on KAFKA-3907: -- Hello Richard, sorry for the late reply. As p

[jira] [Commented] (KAFKA-5697) StreamThread.close() need to interrupt the stream threads to break the loop

[ https://issues.apache.org/jira/browse/KAFKA-5697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285540#comment-16285540 ] Guozhang Wang commented on KAFKA-5697: -- [~johnma] are you still working on this ticke

[jira] [Resolved] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-5318. -- Resolution: Fixed > Streams state may be misleading > --- > >

[jira] [Commented] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285537#comment-16285537 ] Guozhang Wang commented on KAFKA-5318: -- I think it is resolved by KAFKA-5372 already.

[jira] [Updated] (KAFKA-5318) Streams state may be misleading

[ https://issues.apache.org/jira/browse/KAFKA-5318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang updated KAFKA-5318: - Fix Version/s: 1.0.0 > Streams state may be misleading > --- > >

[jira] [Commented] (KAFKA-5551) StreamThread should not expose methods for testing

[ https://issues.apache.org/jira/browse/KAFKA-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285529#comment-16285529 ] Guozhang Wang commented on KAFKA-5551: -- I think this is already resolved by {{TaskMan

[jira] [Assigned] (KAFKA-5676) MockStreamsMetrics should be in o.a.k.test

[ https://issues.apache.org/jira/browse/KAFKA-5676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang reassigned KAFKA-5676: Assignee: Guozhang Wang (was: Chanchal Singh) > MockStreamsMetrics should be in o.a.k.test

[jira] [Commented] (KAFKA-6336) when using assign() with kafka consumer the KafkaConsumerGroup command doesnt show those consumers

[ https://issues.apache.org/jira/browse/KAFKA-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285474#comment-16285474 ] huxihx commented on KAFKA-6336: --- Actually, `listGroups` protocol does return the user-assign

[jira] [Issue Comment Deleted] (KAFKA-5398) Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry

[ https://issues.apache.org/jira/browse/KAFKA-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gavrie Philipson updated KAFKA-5398: Comment: was deleted (was: I posted a question regarding this on the Confluent group: https:

[jira] [Commented] (KAFKA-5398) Joins on GlobalKTable don't work properly when combined with Avro and the Confluent Schema Registry

[ https://issues.apache.org/jira/browse/KAFKA-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285283#comment-16285283 ] Gavrie Philipson commented on KAFKA-5398: - I posted a question regarding this on t

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285159#comment-16285159 ] Ismael Juma commented on KAFKA-3955: I have to look closer, but it seems to me that Lo

[jira] [Updated] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma updated KAFKA-3955: --- Fix Version/s: (was: 1.0.1) 1.1.0 > Kafka log recovery doesn't truncate logs on

[jira] [Assigned] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma reassigned KAFKA-3955: -- Assignee: Ismael Juma > Kafka log recovery doesn't truncate logs on non-monotonic offsets, lead

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285155#comment-16285155 ] Ismael Juma commented on KAFKA-3955: OK, since KAFKA-1211 requires the message format

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285148#comment-16285148 ] James Cheng commented on KAFKA-3955: log.message.format.version = 0.10.0.1 > Kafka lo

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285147#comment-16285147 ] Ismael Juma commented on KAFKA-3955: [~wushujames], what message format version was be

[jira] [Commented] (KAFKA-3955) Kafka log recovery doesn't truncate logs on non-monotonic offsets, leading to failed broker boot

[ https://issues.apache.org/jira/browse/KAFKA-3955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285136#comment-16285136 ] James Cheng commented on KAFKA-3955: We encountered this last week on 0.11.0.1. Thanks