[jira] [Created] (KAFKA-7912) In-memory key-value store does not support concurrent access

Sophie Blee-Goldman created KAFKA-7912: -- Summary: In-memory key-value store does not support concurrent access Key: KAFKA-7912 URL: https://issues.apache.org/jira/browse/KAFKA-7912 Project:

[jira] [Commented] (KAFKA-7466) Implement KIP-339: Create a new IncrementalAlterConfigs API

[ https://issues.apache.org/jira/browse/KAFKA-7466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764001#comment-16764001 ] ASF GitHub Bot commented on KAFKA-7466: --- omkreddy commented on pull request #6247: KAFKA-7466: Add

[jira] [Created] (KAFKA-7911) Add Timezone Support for Windowed Aggregations

Matthias J. Sax created KAFKA-7911: -- Summary: Add Timezone Support for Windowed Aggregations Key: KAFKA-7911 URL: https://issues.apache.org/jira/browse/KAFKA-7911 Project: Kafka Issue Type:

[jira] [Commented] (KAFKA-7864) AdminZkClient.validateTopicCreate() should validate that partitions are 0-based

[ https://issues.apache.org/jira/browse/KAFKA-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763858#comment-16763858 ] ASF GitHub Bot commented on KAFKA-7864: --- ctchenn commented on pull request #6246: KAFKA-7864;

[jira] [Assigned] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish reassigned KAFKA-7909: --- Assignee: Arjun Satish > Coordinator changes cause Connect integration test to fail >

[jira] [Commented] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763812#comment-16763812 ] Arjun Satish commented on KAFKA-7909: - [~ijuma] I believe [this

[jira] [Updated] (KAFKA-7884) Docs for message.format.version and log.message.format.version show invalid (corrupt?) "valid values"

[ https://issues.apache.org/jira/browse/KAFKA-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-7884: --- Fix Version/s: (was: 2.1.1) > Docs for message.format.version and

[jira] [Updated] (KAFKA-7876) Broker suddenly got disconnected

[ https://issues.apache.org/jira/browse/KAFKA-7876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-7876: --- Fix Version/s: (was: 2.1.1) > Broker suddenly got disconnected >

[jira] [Updated] (KAFKA-7880) KafkaConnect should standardize worker thread name

[ https://issues.apache.org/jira/browse/KAFKA-7880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin P. McCabe updated KAFKA-7880: --- Fix Version/s: (was: 2.1.1) > KafkaConnect should standardize worker thread name >

[jira] [Updated] (KAFKA-7897) Invalid use of epoch cache with old message format versions

[ https://issues.apache.org/jira/browse/KAFKA-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson updated KAFKA-7897: --- Summary: Invalid use of epoch cache with old message format versions (was: Invalid use of

[jira] [Commented] (KAFKA-7897) Invalid use of epoch cache following message format downgrade

[ https://issues.apache.org/jira/browse/KAFKA-7897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763766#comment-16763766 ] ASF GitHub Bot commented on KAFKA-7897: --- hachikuji commented on pull request #6232: KAFKA-7897;

[jira] [Commented] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763622#comment-16763622 ] Ismael Juma commented on KAFKA-7909: Thanks for the report. Do you know which change caused this

[jira] [Created] (KAFKA-7910) Document retention.ms behavior with record timestamp

Stanislav Kozlovski created KAFKA-7910: -- Summary: Document retention.ms behavior with record timestamp Key: KAFKA-7910 URL: https://issues.apache.org/jira/browse/KAFKA-7910 Project: Kafka

[jira] [Updated] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-7909: Component/s: core > Coordinator changes cause Connect integration test to fail >

[jira] [Updated] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-7909: Description: We recently introduced integration tests in Connect. This test spins up one or more

[jira] [Updated] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-7909: Component/s: consumer > Coordinator changes cause Connect integration test to fail >

[jira] [Updated] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

[ https://issues.apache.org/jira/browse/KAFKA-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arjun Satish updated KAFKA-7909: Description: We recently introduced integration tests in Connect. This test spins up one or more

[jira] [Created] (KAFKA-7909) Coordinator changes cause Connect integration test to fail

Arjun Satish created KAFKA-7909: --- Summary: Coordinator changes cause Connect integration test to fail Key: KAFKA-7909 URL: https://issues.apache.org/jira/browse/KAFKA-7909 Project: Kafka Issue