jira  

Messages by Thread

• • Re: [PR] KAFKA-20524: CSV reset offset plan for kafka-share-groups.sh [kafka] via GitHub
  • Re: [PR] KAFKA-20524: CSV reset offset plan for kafka-share-groups.sh [kafka] via GitHub
  • Re: [PR] KAFKA-20524: CSV reset offset plan for kafka-share-groups.sh [kafka] via GitHub
• Re: [PR] MINOR: Rewrite ClientOAuthIntegrationTest from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite ClientOAuthIntegrationTest from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite ClientOAuthIntegrationTest from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Rewrite ClientOAuthIntegrationTest from Scala to Java [kafka] via GitHub
• Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20246: Add clusterId and nodeId to ApiVersionsRequest (3/N) [kafka] via GitHub
• [jira] [Created] (KAFKA-20700) AllowedPaths should resolve symlinks before validating paths against allowed.paths Nilesh Kumar (Jira)
• [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
  • Re: [PR] KAFKA-20699: TopologyTestDriver.getStateStore must not reset the record context [kafka] via GitHub
• [jira] [Created] (KAFKA-20699) TopologyTestDriver.getStateStore corrupts the task's record context Jira
• Re: [PR] KAFKA-20522: Refine test coverage for consumer close-on-interrupt best-effort behavior. [kafka] via GitHub
  • Re: [PR] KAFKA-20522: Refine test coverage for consumer close-on-interrupt best-effort behavior. [kafka] via GitHub
  • Re: [PR] KAFKA-20522: Refine test coverage for consumer close-on-interrupt best-effort behavior. [kafka] via GitHub
  • Re: [PR] KAFKA-20522: Refine test coverage for consumer close-on-interrupt best-effort behavior. [kafka] via GitHub
  • Re: [PR] KAFKA-20522: Refine test coverage for consumer close-on-interrupt best-effort behavior. [kafka] via GitHub
• [PR] MINOR: Simplify AlterPartitionManager request building and tests [kafka] via GitHub
  • Re: [PR] MINOR: Simplify AlterPartitionManager request building and tests [kafka] via GitHub
• Re: [PR] MINOR: Speed up ShareConsumerTest.testAcquisitionLockTimeoutOnConsumer [kafka] via GitHub
  • Re: [PR] MINOR: Speed up ShareConsumerTest.testAcquisitionLockTimeoutOnConsumer [kafka] via GitHub
• [jira] [Updated] (KAFKA-20694) Fix share coordinator readState leaderEpoch -1 sentinel fencing Andrew Schofield (Jira)
  • [jira] [Updated] (KAFKA-20694) Fix share coordinator readState leaderEpoch -1 sentinel fencing Lianet Magrans (Jira)
• [jira] [Resolved] (KAFKA-20694) Fix share coordinator readState leaderEpoch -1 sentinel fencing Andrew Schofield (Jira)
• Re: [PR] KAFKA-20694: Fix share read leader epoch sentinel [kafka] via GitHub
  • Re: [PR] KAFKA-20694: Fix share read leader epoch sentinel [kafka] via GitHub
• Re: [PR] KAFKA-20116: Send task-(end)-offset to broker (1/N) [kafka] via GitHub
  • Re: [PR] KAFKA-20116: Send task-(end)-offset to broker (1/N) [kafka] via GitHub
• Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
  • Re: [PR] KAFKA-20633: Update the default value of remote copy lag bytes [kafka] via GitHub
• [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
  • Re: [PR] KAFKA-20693: fix npe in abstract herder when no config value [kafka] via GitHub
• Re: [PR] KAFKA-20673: Skip stale-leader lookup retry while the AdminClient is closing (follow-up) [kafka] via GitHub
  • Re: [PR] KAFKA-20673: Skip stale-leader lookup retry while the AdminClient is closing (follow-up) [kafka] via GitHub
• Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Add ducktape test code for Streams Rebalance Protocol. [kafka] via GitHub
• Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
  • Re: [PR] KAFKA-20623: Update RPC for streams group topology description plugin (2/3) [kafka] via GitHub
• Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Client Side. [kafka] via GitHub
• Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Server Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Server Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Server Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Server Side. [kafka] via GitHub
  • Re: [PR] KAFKA-20169: Support static membership for Kafka Streams with the streams rebalance protocol at Server Side. [kafka] via GitHub
• Re: [PR] KAFKA-20623: Heartbeat extension for streams group topology description plugin (1/3) [kafka] via GitHub
• [jira] [Updated] (KAFKA-20693) NPE in error handling in AbstractHerder Gaetan Collaud (Jira)
• Re: [PR] Mm2 fault tolerance enhancement [kafka] via GitHub
  • Re: [PR] Mm2 fault tolerance enhancement [kafka] via GitHub
• Re: [PR] KAFKA-20270 [kafka] via GitHub
  • Re: [PR] KAFKA-20270 [kafka] via GitHub
  • Re: [PR] KAFKA-20270 [kafka] via GitHub
• Re: [PR] KAFKA-19983: Fix MockProcessorContext doesn't work with WindowStores. [kafka] via GitHub
  • Re: [PR] KAFKA-19983: Fix MockProcessorContext doesn't work with WindowStores. [kafka] via GitHub
  • Re: [PR] KAFKA-19983: Fix MockProcessorContext doesn't work with WindowStores. [kafka] via GitHub
• Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
  • Re: [PR] KAFKA-20088: CIDR-based Host Patterns for ACLs [kafka] via GitHub
• Re: [PR] KAFKA-20658: Fix Cast ByteBuffer BYTES to string encoding [kafka] via GitHub
• Re: [PR] KAFKA-20676: do not fail startup when a non-supported user configured cipher is used [kafka] via GitHub
• Re: [PR] KAFKA-20659: Reject unsupported MirrorMaker record versions at runtime [kafka] via GitHub
  • Re: [PR] KAFKA-20659: Reject unsupported MirrorMaker record versions at runtime [kafka] via GitHub
  • Re: [PR] KAFKA-20659: Reject unsupported MirrorMaker record versions at runtime [kafka] via GitHub
• Re: [PR] MINOR: Move transaction coordinator leaf classes from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Move transaction coordinator leaf classes from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Move transaction coordinator leaf classes from Scala to Java [kafka] via GitHub
  • Re: [PR] MINOR: Move transaction coordinator leaf classes from Scala to Java [kafka] via GitHub
• Re: [PR] MINOR: Split KafkaAdminClientTest into per-domain test classes [kafka] via GitHub
• Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
  • Re: [PR] KAFKA-20668: Add --checkpoint option to kafka-metadata-shell [kafka] via GitHub
• Re: [PR] KAFKA-20677: Enhance test coverage of testCannotSendToInternalTopic [kafka] via GitHub
  • Re: [PR] KAFKA-20677: Enhance test coverage of testCannotSendToInternalTopic [kafka] via GitHub
  • Re: [PR] KAFKA-20677: Enhance test coverage of testCannotSendToInternalTopic [kafka] via GitHub
• [jira] [Assigned] (KAFKA-20677) Enhance the test coverage of testCannotSendToInternalTopic Ming-Yen Chung (Jira)
  • [jira] [Assigned] (KAFKA-20677) Enhance the test coverage of testCannotSendToInternalTopic Ming-Yen Chung (Jira)
  • [jira] [Assigned] (KAFKA-20677) Enhance the test coverage of testCannotSendToInternalTopic Ming-Yen Chung (Jira)
• [jira] [Created] (KAFKA-20698) Remove deprecated ConsumerRecords(Map) constructor Evan Zhou (Jira)
• Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
  • Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
  • Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
  • Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
  • Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
  • Re: [PR] KSTREAMS-8781: Add back `rack.aware.assignment.tags` config [kafka] via GitHub
• [PR] Gradle 10 migration/20260615 2121 g951 to papi 20260609 [kafka] via GitHub
  • Re: [PR] Gradle 10 migration/20260615 2121 g951 to papi 20260609 [kafka] via GitHub
  • Re: [PR] Gradle 10 migration/20260615 2121 g951 to papi 20260609 [kafka] via GitHub
• Re: [PR] KAFKA-20116: WIP [kafka] via GitHub
  • Re: [PR] KAFKA-20116: WIP [kafka] via GitHub
• Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub
  • Re: [PR] KAFKA-20514: kraft observers should use previous fetch response to decide where to send the next fetch [kafka] via GitHub

• Later messages