[jira] [Created] (KAFKA-12712) KRaft: Missing controller.quorom.voters config not properly handled

Magnus Edenhill created KAFKA-12712: --- Summary: KRaft: Missing controller.quorom.voters config not properly handled Key: KAFKA-12712 URL: https://issues.apache.org/jira/browse/KAFKA-12712 Project:

[jira] [Commented] (KAFKA-10507) Limit the set of APIs returned in pre-authentication ApiVersions

[ https://issues.apache.org/jira/browse/KAFKA-10507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1716#comment-1716 ] Magnus Edenhill commented on KAFKA-10507: - librdkafka will only send ApiVersionRequests prior to

[jira] [Closed] (KAFKA-9180) Broker won't start with empty log dir

[ https://issues.apache.org/jira/browse/KAFKA-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill closed KAFKA-9180. -- > Broker won't start with empty log dir > - > >

[jira] [Resolved] (KAFKA-9180) Broker won't start with empty log dir

[ https://issues.apache.org/jira/browse/KAFKA-9180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill resolved KAFKA-9180. Resolution: Invalid Turned out to be old client jars making a mess.   > Broker won't

[jira] [Created] (KAFKA-9180) Broker won't start with empty log dir

Magnus Edenhill created KAFKA-9180: -- Summary: Broker won't start with empty log dir Key: KAFKA-9180 URL: https://issues.apache.org/jira/browse/KAFKA-9180 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-7549) Old ProduceRequest with zstd compression does not return error to client

[ https://issues.apache.org/jira/browse/KAFKA-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667263#comment-16667263 ] Magnus Edenhill commented on KAFKA-7549: Right, but the producer client will hopefully expose the

[jira] [Commented] (KAFKA-7549) Old ProduceRequest with zstd compression does not return error to client

[ https://issues.apache.org/jira/browse/KAFKA-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1859#comment-1859 ] Magnus Edenhill commented on KAFKA-7549: Even if option 2 is logically more correct, I believe

[jira] [Created] (KAFKA-7549) Old ProduceRequest with zstd compression does not return error to client

Magnus Edenhill created KAFKA-7549: -- Summary: Old ProduceRequest with zstd compression does not return error to client Key: KAFKA-7549 URL: https://issues.apache.org/jira/browse/KAFKA-7549 Project:

[jira] [Resolved] (KAFKA-6885) DescribeConfigs synonyms are are identical to parent entry for BROKER resources

[ https://issues.apache.org/jira/browse/KAFKA-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Magnus Edenhill resolved KAFKA-6885. Resolution: Invalid > DescribeConfigs synonyms are are identical to parent entry for BROKER

[jira] [Commented] (KAFKA-6885) DescribeConfigs synonyms are are identical to parent entry for BROKER resources

[ https://issues.apache.org/jira/browse/KAFKA-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16468573#comment-16468573 ] Magnus Edenhill commented on KAFKA-6885: Okay, I think I understand, the choice of "synonym" is a

[jira] [Created] (KAFKA-6885) DescribeConfigs synonyms are are identical to parent entry for BROKER resources

Magnus Edenhill created KAFKA-6885: -- Summary: DescribeConfigs synonyms are are identical to parent entry for BROKER resources Key: KAFKA-6885 URL: https://issues.apache.org/jira/browse/KAFKA-6885

[jira] [Created] (KAFKA-6778) DescribeConfigs does not return error for non-existent topic

Magnus Edenhill created KAFKA-6778: -- Summary: DescribeConfigs does not return error for non-existent topic Key: KAFKA-6778 URL: https://issues.apache.org/jira/browse/KAFKA-6778 Project: Kafka

[jira] [Commented] (KAFKA-4974) System test failure in 0.8.2.2 upgrade tests

[ https://issues.apache.org/jira/browse/KAFKA-4974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16387689#comment-16387689 ] Magnus Edenhill commented on KAFKA-4974: Haven't seen it since, this issue can probably be closed.