jira  

Messages by Thread

• • Re: [PR] MINOR:Remove explicit flushes from RocksDBStores [kafka] via GitHub
  • Re: [PR] MINOR:Remove explicit flushes from RocksDBStores [kafka] via GitHub
  • Re: [PR] MINOR:Remove explicit flushes from RocksDBStores [kafka] via GitHub
  • Re: [PR] MINOR:Remove explicit flushes from RocksDBStores [kafka] via GitHub
• [PR] KAFKA-20193: Remove `static <T> T value(...)` method from ValueTimestampHeadersDeserializer if not needed [kafka] via GitHub
  • Re: [PR] KAFKA-20193: Remove `static <T> T value(...)` method from ValueTimestampHeadersDeserializer if not needed [kafka] via GitHub
  • Re: [PR] KAFKA-20193: Remove `static <T> T value(...)` method from ValueTimestampHeadersDeserializer if not needed [kafka] via GitHub
  • Re: [PR] KAFKA-20193: Remove `static <T> T value(...)` method from ValueTimestampHeadersDeserializer if not needed [kafka] via GitHub
• Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
  • Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
  • Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
  • Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
  • Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
  • Re: [PR] KAFKA-20289: Fix DescribeConfigs to correctly resolve broker synonyms for group configs [kafka] via GitHub
• Re: [PR] KAFKA-19712: Commit OFFSET_UNKOWN when closing state stores and the offsets are not yet initialized [kafka] via GitHub
  • Re: [PR] KAFKA-19712: Commit OFFSET_UNKOWN when closing state stores and the offsets are not yet initialized [kafka] via GitHub
  • Re: [PR] KAFKA-19712: Commit OFFSET_UNKOWN when closing state stores and the offsets are not yet initialized [kafka] via GitHub
• Re: [PR] MINOR: Test Coverage for Segmented stores [kafka] via GitHub
  • Re: [PR] MINOR: Test Coverage for Segmented stores [kafka] via GitHub
  • Re: [PR] MINOR: Test Coverage for Segmented stores [kafka] via GitHub
• [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: kraft.version=0 leaders should advertise their endpoint from controller.quorum.voters [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
  • Re: [PR] KAFKA-20380: controller.quorum.voters should act as advertised.listeners if the latter is not defined [kafka] via GitHub
• Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
  • Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
  • Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
  • Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
  • Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
  • Re: [PR] KAFKA-19863: Add documentation on how to implement a custom exception(with ref to DLQ) [kafka] via GitHub
• Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
  • Re: [PR] Address KAFKA-20252: Migrate clearYammerMetrics to TestUtils [kafka] via GitHub
• Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
  • Re: [PR] KAFKA-20194: Ensure backward compatibility [kafka] via GitHub
• [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat sanghyeok An (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Andrew Schofield (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
  • [jira] [Commented] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
• [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Matthias J. Sax (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Matthias J. Sax (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store PoAn Yang (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Ray McDermott (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store PoAn Yang (Jira)
  • [jira] [Commented] (KAFKA-19638) NPE in `Processor#init()` accessing state store Matthias J. Sax (Jira)
• [jira] [Commented] (KAFKA-17789) State updater stuck when starting with empty state folder Nikita Shupletsov (Jira)
  • [jira] [Commented] (KAFKA-17789) State updater stuck when starting with empty state folder Antoine Michaud (Jira)
  • [jira] [Commented] (KAFKA-17789) State updater stuck when starting with empty state folder Nikita Shupletsov (Jira)
  • [jira] [Commented] (KAFKA-17789) State updater stuck when starting with empty state folder Lucas Brutschy (Jira)
  • [jira] [Commented] (KAFKA-17789) State updater stuck when starting with empty state folder Antoine Michaud (Jira)
• [jira] [Assigned] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
• [jira] [Created] (KAFKA-20381) Producer Transaction Session Heartbeat Shekhar Prasad Rajak (Jira)
• [jira] [Resolved] (KAFKA-20361) Fix LazyDownConversionRecordsTest in using zlib-ng Chia-Ping Tsai (Jira)
• Re: [PR] KAFKA-20361 : Fix LazyDownConversionRecordsTest in using zlib-ng [kafka] via GitHub
• [jira] [Created] (KAFKA-20380) controller.quorum.voters should act as advertised.listeners for kraft.version=0 Kevin Wu (Jira)
• [jira] [Created] (KAFKA-20379) ducker-ak has no option to skip the gradlew systemTestLibs build step Maros Orsak (Jira)
• [jira] [Created] (KAFKA-20378) ducker-ak container memory limit is hardcoded Maros Orsak (Jira)
• [jira] [Commented] (KAFKA-20334) Consider to update KStream-KStream join to use plain-value-header-window stores PoAn Yang (Jira)
• [PR] MINOR: Add todo to WindowSegmentWithHeaders [kafka] via GitHub
  • Re: [PR] MINOR: Add todo to WindowSegmentWithHeaders [kafka] via GitHub
• Re: [PR] KAFKA-14487: Move LogManager to storage module [kafka] via GitHub
  • Re: [PR] KAFKA-14487: Move LogManager to storage module [kafka] via GitHub
• [jira] [Created] (KAFKA-20377) ducker-ak does not support passing additional Docker build arguments Maros Orsak (Jira)
• Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
  • Re: [PR] KAFKA-19193 Support rack-aware partitioning for Kafka producer [kafka] via GitHub
• [PR] MINOR: Cleanups in LogManager [kafka] via GitHub
  • Re: [PR] MINOR: Cleanups in LogManager [kafka] via GitHub
• [PR] KAFKA 18965 release validation kafka clients [kafka] via GitHub
  • Re: [PR] KAFKA-18965 release validation kafka clients [kafka] via GitHub
  • Re: [PR] KAFKA-18965 release validation kafka clients [kafka] via GitHub
  • Re: [PR] KAFKA-18965 release validation kafka clients [kafka] via GitHub
• Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
  • Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
  • Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
  • Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
  • Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
  • Re: [PR] KAFKA-20371: Add Iterable constructor to generated message collections [kafka] via GitHub
• [PR] KAFKA-20094: Add sanity test coverage for default configuration (no environment variables) [kafka] via GitHub
• Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
  • Re: [PR] KAFKA-13499: Avoid restoring outdated records [kafka] via GitHub
• [jira] [Updated] (KAFKA-20376) Update site docs for rebalance protocol page Lianet Magrans (Jira)
  • [jira] [Updated] (KAFKA-20376) Update site docs for rebalance protocol page Lianet Magrans (Jira)
  • [jira] [Updated] (KAFKA-20376) Update site docs for rebalance protocol page Lianet Magrans (Jira)
  • [jira] [Updated] (KAFKA-20376) Update site docs for rebalance protocol page Lianet Magrans (Jira)
• Re: [PR] KAFKA-20297: move ImplicitLinkedHashCollection, ImplicitLinkedHashMultiCollection, and ByteUtils from utils to internals [kafka] via GitHub
• [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
  • Re: [PR] KAFKA-20297: move testIncrement and testIncrementUpperBoundary to ByteUtilsTest [kafka] via GitHub
• Re: [PR] MINOR: Cherry pick important fixes for 4.2.1 [kafka] via GitHub
• Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
  • Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
  • Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
  • Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
  • Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
  • Re: [PR] KAFKA-20119: Clarify that `Consumer#unsubscribe` does not trigger auto-commit [kafka] via GitHub
• [jira] [Created] (KAFKA-20376) Update site docs for rebalance protocol page Lianet Magrans (Jira)
• Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
  • Re: [PR] KAFKA-20282: Add message to classic consumer startup guiding to next-gen protocol [kafka] via GitHub
• [PR] KAFKA-20336: Add documentation for KIP-1285 DSL headers-aware state s… [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
  • Re: [PR] KAFKA-20336: Add documentation DSL headers-aware state stores [kafka] via GitHub
• Re: [PR] MINOR: Sort reviewer candidates by contribution count [kafka] via GitHub
  • Re: [PR] MINOR: Sort reviewer candidates by contribution count [kafka] via GitHub
  • Re: [PR] MINOR: Sort reviewer candidates by contribution count [kafka] via GitHub
  • Re: [PR] MINOR: Sort reviewer candidates by contribution count [kafka] via GitHub
• Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
  • Re: [PR] KAFKA-20332: Fix to ensure app thread not collecting records for partitions being revoked [kafka] via GitHub
• [PR] KAFKA-19752 Move parts of UnifiedLogTest to storage module [kafka] via GitHub
  • Re: [PR] KAFKA-19752 Move parts of UnifiedLogTest to storage module [kafka] via GitHub
  • Re: [PR] KAFKA-19752 Move parts of UnifiedLogTest to storage module [kafka] via GitHub
  • Re: [PR] KAFKA-19752 Move parts of UnifiedLogTest to storage module [kafka] via GitHub
• Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub
  • Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub
  • Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub
  • Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub
  • Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub
  • Re: [PR] KAFKA-19937: Introduced Shared ReaperThread for Persister / NetworkPartitionMetadataClient [kafka] via GitHub

• Later messages