[jira] [Commented] (KAFKA-17101) Mirror maker internal topics cleanup policy changes to 'delete' from 'compact'

[ https://issues.apache.org/jira/browse/KAFKA-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868990#comment-17868990 ] Chris Egerton commented on KAFKA-17101: --- Spoke too soon–looks like the test failures we're seeing

[jira] [Commented] (KAFKA-17101) Mirror maker internal topics cleanup policy changes to 'delete' from 'compact'

[ https://issues.apache.org/jira/browse/KAFKA-17101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868837#comment-17868837 ] Chris Egerton commented on KAFKA-17101: --- [~kaushik srinivas] Are your Kafka clusters running in

[jira] [Commented] (KAFKA-17174) Migrate OffsetsApiIntegrationTest to use ClusterTestExtensions

[ https://issues.apache.org/jira/browse/KAFKA-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868460#comment-17868460 ] Chris Egerton commented on KAFKA-17174: --- {quote}{color:#172b4d}Unfortunately, fragment must happen

[jira] [Comment Edited] (KAFKA-17174) Migrate OffsetsApiIntegrationTest to use ClusterTestExtensions

[ https://issues.apache.org/jira/browse/KAFKA-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868460#comment-17868460 ] Chris Egerton edited comment on KAFKA-17174 at 7/24/24 7:04 PM:

[jira] [Updated] (KAFKA-16445) PATCH method for connector configuration

[ https://issues.apache.org/jira/browse/KAFKA-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16445: -- Issue Type: New Feature (was: Improvement) > PATCH method for connector configuration >

[jira] [Resolved] (KAFKA-16068) Use TestPlugins in ConnectorValidationIntegrationTest to silence plugin scanning errors

[ https://issues.apache.org/jira/browse/KAFKA-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16068. --- Fix Version/s: 3.9.0 Resolution: Fixed > Use TestPlugins in

[jira] [Commented] (KAFKA-17174) Migrate OffsetsApiIntegrationTest to use ClusterTestExtensions

[ https://issues.apache.org/jira/browse/KAFKA-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868132#comment-17868132 ] Chris Egerton commented on KAFKA-17174: --- I've left my thoughts on the PR I linked above, but

[jira] [Commented] (KAFKA-17174) Migrate OffsetsApiIntegrationTest to use ClusterTestExtensions

[ https://issues.apache.org/jira/browse/KAFKA-17174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867659#comment-17867659 ] Chris Egerton commented on KAFKA-17174: --- I'm not sure this is the right direction to go in.

[jira] [Commented] (KAFKA-16068) Use TestPlugins in ConnectorValidationIntegrationTest to silence plugin scanning errors

[ https://issues.apache.org/jira/browse/KAFKA-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867411#comment-17867411 ] Chris Egerton commented on KAFKA-16068: --- @johndoe I've reassigned this to myself; let me know if

[jira] [Assigned] (KAFKA-16068) Use TestPlugins in ConnectorValidationIntegrationTest to silence plugin scanning errors

[ https://issues.apache.org/jira/browse/KAFKA-16068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-16068: - Assignee: Chris Egerton (was: johndoe) > Use TestPlugins in

[jira] [Commented] (KAFKA-17044) Connector deletion can lead to resource leak during a long running connector startup

[ https://issues.apache.org/jira/browse/KAFKA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867397#comment-17867397 ] Chris Egerton commented on KAFKA-17044: --- The crux of the issue is that invoking {{stop}} on a

[jira] [Updated] (KAFKA-17105) Unnecessary connector restarts after being newly created

[ https://issues.apache.org/jira/browse/KAFKA-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-17105: -- Fix Version/s: 3.9.0 > Unnecessary connector restarts after being newly created >

[jira] [Resolved] (KAFKA-17105) Unnecessary connector restarts after being newly created

[ https://issues.apache.org/jira/browse/KAFKA-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-17105. --- Resolution: Fixed > Unnecessary connector restarts after being newly created >

[jira] [Updated] (KAFKA-17155) Redundant rebalances triggered after connector creation/deletion and task config updates

[ https://issues.apache.org/jira/browse/KAFKA-17155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-17155: -- Description: With KAFKA-17105, a scenario is described where a connector may be

[jira] [Created] (KAFKA-17155) Redundant rebalances triggered after connector creation/deletion and task config updates

Chris Egerton created KAFKA-17155: - Summary: Redundant rebalances triggered after connector creation/deletion and task config updates Key: KAFKA-17155 URL: https://issues.apache.org/jira/browse/KAFKA-17155

[jira] [Resolved] (KAFKA-16383) fix flaky test IdentityReplicationIntegrationTest.testReplicateFromLatest()

[ https://issues.apache.org/jira/browse/KAFKA-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16383. --- Resolution: Fixed > fix flaky test

[jira] [Commented] (KAFKA-17145) Reinstate Utils.join() method in org.apache.kafka.common.utils

[ https://issues.apache.org/jira/browse/KAFKA-17145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866449#comment-17866449 ] Chris Egerton commented on KAFKA-17145: --- IMO this does not warrant a new RC, nor should it be

[jira] [Resolved] (KAFKA-14401) Connector/Tasks reading offsets can get stuck if underneath WorkThread dies

[ https://issues.apache.org/jira/browse/KAFKA-14401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-14401. --- Fix Version/s: 3.9.0 Resolution: Fixed > Connector/Tasks reading offsets can get

[jira] [Commented] (KAFKA-17044) Connector deletion can lead to resource leak during a long running connector startup

[ https://issues.apache.org/jira/browse/KAFKA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866188#comment-17866188 ] Chris Egerton commented on KAFKA-17044: --- [~bgoyal] please let me know if the workaround suggested

[jira] [Assigned] (KAFKA-15892) Flaky test: testAlterSinkConnectorOffsets – org.apache.kafka.connect.integration.OffsetsApiIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-15892: - Assignee: Chris Egerton > Flaky test: testAlterSinkConnectorOffsets – >

[jira] [Commented] (KAFKA-16383) fix flaky test IdentityReplicationIntegrationTest.testReplicateFromLatest()

[ https://issues.apache.org/jira/browse/KAFKA-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866180#comment-17866180 ] Chris Egerton commented on KAFKA-16383: --- I think I've found the root cause, so I've reassigned to

[jira] [Assigned] (KAFKA-16383) fix flaky test IdentityReplicationIntegrationTest.testReplicateFromLatest()

[ https://issues.apache.org/jira/browse/KAFKA-16383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-16383: - Assignee: Chris Egerton (was: Johnny Hsu) > fix flaky test

[jira] [Commented] (KAFKA-14569) Migrate EmbeddedKafkaCluster used by Connect integration tests from EmbeddedZookeeper to KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866142#comment-17866142 ] Chris Egerton commented on KAFKA-14569: --- I've upgraded the priority to blocker since we'll need to

[jira] [Assigned] (KAFKA-14569) Migrate EmbeddedKafkaCluster used by Connect integration tests from EmbeddedZookeeper to KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-14569: - Assignee: Chris Egerton > Migrate EmbeddedKafkaCluster used by Connect integration

[jira] [Updated] (KAFKA-14569) Migrate EmbeddedKafkaCluster used by Connect integration tests from EmbeddedZookeeper to KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-14569: -- Fix Version/s: 4.0.0 > Migrate EmbeddedKafkaCluster used by Connect integration tests from >

[jira] [Updated] (KAFKA-14569) Migrate EmbeddedKafkaCluster used by Connect integration tests from EmbeddedZookeeper to KRaft

[ https://issues.apache.org/jira/browse/KAFKA-14569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-14569: -- Priority: Blocker (was: Minor) > Migrate EmbeddedKafkaCluster used by Connect integration

[jira] [Created] (KAFKA-17130) Connect workers do not properly ensure group membership before responding to health checks

Chris Egerton created KAFKA-17130: - Summary: Connect workers do not properly ensure group membership before responding to health checks Key: KAFKA-17130 URL: https://issues.apache.org/jira/browse/KAFKA-17130

[jira] [Assigned] (KAFKA-17105) Unnecessary connector restarts after being newly created

[ https://issues.apache.org/jira/browse/KAFKA-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-17105: - Assignee: Chris Egerton > Unnecessary connector restarts after being newly created >

[jira] [Updated] (KAFKA-17115) Closing newly-created consumers during rebalance can cause rebalances to hang

[ https://issues.apache.org/jira/browse/KAFKA-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-17115: -- Description: When a dynamic consumer (i.e., one with no group instance ID configured) first

[jira] [Updated] (KAFKA-17115) Closing newly-created legacy consumers during rebalance can cause rebalances to hang

[ https://issues.apache.org/jira/browse/KAFKA-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-17115: -- Summary: Closing newly-created legacy consumers during rebalance can cause rebalances to hang

[jira] [Commented] (KAFKA-17115) Closing newly-created consumers during rebalance can cause rebalances to hang

[ https://issues.apache.org/jira/browse/KAFKA-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864870#comment-17864870 ] Chris Egerton commented on KAFKA-17115: --- Damn, that was fast! Thanks for the follow-up [~lianetm],

[jira] [Created] (KAFKA-17115) Closing newly-created consumers during rebalance can cause rebalances to hang

Chris Egerton created KAFKA-17115: - Summary: Closing newly-created consumers during rebalance can cause rebalances to hang Key: KAFKA-17115 URL: https://issues.apache.org/jira/browse/KAFKA-17115

[jira] [Commented] (KAFKA-17105) Unnecessary connector restarts after being newly created

[ https://issues.apache.org/jira/browse/KAFKA-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17864415#comment-17864415 ] Chris Egerton commented on KAFKA-17105: --- This likely goes back much further than 3.0.0. To save

[jira] [Updated] (KAFKA-17105) Unnecessary connector restarts after being newly created

[ https://issues.apache.org/jira/browse/KAFKA-17105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-17105: -- Description: When a connector is created, it may be restarted unnecessarily immediately

[jira] [Created] (KAFKA-17105) Unnecessary connector restarts after being newly created

Chris Egerton created KAFKA-17105: - Summary: Unnecessary connector restarts after being newly created Key: KAFKA-17105 URL: https://issues.apache.org/jira/browse/KAFKA-17105 Project: Kafka

[jira] [Comment Edited] (KAFKA-17044) Connector deletion can lead to resource leak during a long running connector startup

[ https://issues.apache.org/jira/browse/KAFKA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863559#comment-17863559 ] Chris Egerton edited comment on KAFKA-17044 at 7/7/24 11:31 AM:

[jira] [Comment Edited] (KAFKA-17044) Connector deletion can lead to resource leak during a long running connector startup

[ https://issues.apache.org/jira/browse/KAFKA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863559#comment-17863559 ] Chris Egerton edited comment on KAFKA-17044 at 7/7/24 11:31 AM:

[jira] [Commented] (KAFKA-17044) Connector deletion can lead to resource leak during a long running connector startup

[ https://issues.apache.org/jira/browse/KAFKA-17044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17863559#comment-17863559 ] Chris Egerton commented on KAFKA-17044: --- [~bgoyal] I think you should reconsider the

[jira] [Created] (KAFKA-17075) Use health check endpoint to verify Connect worker readiness in system tests

Chris Egerton created KAFKA-17075: - Summary: Use health check endpoint to verify Connect worker readiness in system tests Key: KAFKA-17075 URL: https://issues.apache.org/jira/browse/KAFKA-17075

[jira] [Resolved] (KAFKA-10816) Connect REST API should have a resource that can be used as a readiness probe

[ https://issues.apache.org/jira/browse/KAFKA-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-10816. --- Fix Version/s: 3.9.0 Resolution: Done > Connect REST API should have a resource that

[jira] [Commented] (KAFKA-15917) Flaky test - OffsetsApiIntegrationTest.testAlterSinkConnectorOffsetsZombieSinkTasks

[ https://issues.apache.org/jira/browse/KAFKA-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862808#comment-17862808 ] Chris Egerton commented on KAFKA-15917: --- Should be partially addressed by

[jira] [Assigned] (KAFKA-15524) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest.testResetSinkConnectorOffsetsZombieSinkTasks

[ https://issues.apache.org/jira/browse/KAFKA-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-15524: - Assignee: (was: Chris Egerton) > Flaky test >

[jira] [Reopened] (KAFKA-15524) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest.testResetSinkConnectorOffsetsZombieSinkTasks

[ https://issues.apache.org/jira/browse/KAFKA-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-15524: --- > Flaky test >

[jira] [Resolved] (KAFKA-15524) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest.testResetSinkConnectorOffsetsZombieSinkTasks

[ https://issues.apache.org/jira/browse/KAFKA-15524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15524. --- Resolution: Later > Flaky test >

[jira] [Assigned] (KAFKA-17049) Incremental rebalances assign too many tasks for the same connector together

[ https://issues.apache.org/jira/browse/KAFKA-17049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-17049: - Assignee: yazgoo > Incremental rebalances assign too many tasks for the same connector

[jira] [Commented] (KAFKA-14021) MirrorMaker 2 should implement KIP-618 APIs

[ https://issues.apache.org/jira/browse/KAFKA-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860185#comment-17860185 ] Chris Egerton commented on KAFKA-14021: --- No, the consumer does not rely on committed offsets for

[jira] [Commented] (KAFKA-14021) MirrorMaker 2 should implement KIP-618 APIs

[ https://issues.apache.org/jira/browse/KAFKA-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860163#comment-17860163 ] Chris Egerton commented on KAFKA-14021: --- The {{MirrorSourceTask::commit}} method doesn't actually

[jira] [Commented] (KAFKA-14021) MirrorMaker 2 should implement KIP-618 APIs

[ https://issues.apache.org/jira/browse/KAFKA-14021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17860157#comment-17860157 ] Chris Egerton commented on KAFKA-14021: --- [~kumarpritam8634] the exactly-once guarantees for the

[jira] [Resolved] (KAFKA-16949) System test test_dynamic_logging in connect_distributed_test is failing

[ https://issues.apache.org/jira/browse/KAFKA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16949. --- Fix Version/s: 3.9.0 Resolution: Fixed > System test test_dynamic_logging in

[jira] [Commented] (KAFKA-16943) Synchronously verify Connect worker startup failure in InternalTopicsIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17856531#comment-17856531 ] Chris Egerton commented on KAFKA-16943: --- [~ksolves.kafka] the idea here isn't to assert that no

[jira] [Assigned] (KAFKA-14089) Flaky ExactlyOnceSourceIntegrationTest.testSeparateOffsetsTopic

[ https://issues.apache.org/jira/browse/KAFKA-14089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-14089: - Fix Version/s: 3.8.0 (was: 3.3.0) Assignee: Chris

[jira] [Commented] (KAFKA-14089) Flaky ExactlyOnceSourceIntegrationTest.testSeparateOffsetsTopic

[ https://issues.apache.org/jira/browse/KAFKA-14089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855668#comment-17855668 ] Chris Egerton commented on KAFKA-14089: --- Should be fixed by

[jira] [Commented] (KAFKA-10816) Connect REST API should have a resource that can be used as a readiness probe

[ https://issues.apache.org/jira/browse/KAFKA-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17855084#comment-17855084 ] Chris Egerton commented on KAFKA-10816: --- I've published

[jira] [Resolved] (KAFKA-16935) Automatically wait for cluster startup in embedded Connect integration tests

[ https://issues.apache.org/jira/browse/KAFKA-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16935. --- Resolution: Fixed > Automatically wait for cluster startup in embedded Connect integration

[jira] [Reopened] (KAFKA-16935) Automatically wait for cluster startup in embedded Connect integration tests

[ https://issues.apache.org/jira/browse/KAFKA-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-16935: --- > Automatically wait for cluster startup in embedded Connect integration tests >

[jira] [Updated] (KAFKA-16935) Automatically wait for cluster startup in embedded Connect integration tests

[ https://issues.apache.org/jira/browse/KAFKA-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16935: -- Fix Version/s: 3.8.0 > Automatically wait for cluster startup in embedded Connect integration

[jira] [Updated] (KAFKA-16943) Synchronously verify Connect worker startup failure in InternalTopicsIntegrationTest

[ https://issues.apache.org/jira/browse/KAFKA-16943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16943: -- Labels: newbie (was: ) > Synchronously verify Connect worker startup failure in >

[jira] [Created] (KAFKA-16943) Synchronously verify Connect worker startup failure in InternalTopicsIntegrationTest

Chris Egerton created KAFKA-16943: - Summary: Synchronously verify Connect worker startup failure in InternalTopicsIntegrationTest Key: KAFKA-16943 URL: https://issues.apache.org/jira/browse/KAFKA-16943

[jira] [Created] (KAFKA-16935) Automatically wait for cluster startup in embedded Connect integration tests

Chris Egerton created KAFKA-16935: - Summary: Automatically wait for cluster startup in embedded Connect integration tests Key: KAFKA-16935 URL: https://issues.apache.org/jira/browse/KAFKA-16935

[jira] [Commented] (KAFKA-16931) Transient REST failures to forward fenceZombie requests leave Connect Tasks in FAILED state

[ https://issues.apache.org/jira/browse/KAFKA-16931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854113#comment-17854113 ] Chris Egerton commented on KAFKA-16931: --- Spoke too soon, have one more thought! [~ecomar] it

[jira] [Comment Edited] (KAFKA-16931) Transient REST failures to forward fenceZombie requests leave Connect Tasks in FAILED state

[ https://issues.apache.org/jira/browse/KAFKA-16931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854091#comment-17854091 ] Chris Egerton edited comment on KAFKA-16931 at 6/11/24 3:09 PM: First,

[jira] [Comment Edited] (KAFKA-16931) Transient REST failures to forward fenceZombie requests leave Connect Tasks in FAILED state

[ https://issues.apache.org/jira/browse/KAFKA-16931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854091#comment-17854091 ] Chris Egerton edited comment on KAFKA-16931 at 6/11/24 3:06 PM: First,

[jira] [Commented] (KAFKA-16931) Transient REST failures to forward fenceZombie requests leave Connect Tasks in FAILED state

[ https://issues.apache.org/jira/browse/KAFKA-16931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17854091#comment-17854091 ] Chris Egerton commented on KAFKA-16931: --- First, one small clarification: task restarts do not

[jira] [Updated] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-9228: - Fix Version/s: 3.7.1 > Reconfigured converters and clients may not be propagated to connector

[jira] [Updated] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-9228: - Fix Version/s: 3.8.0 (was: 4.0.0) > Reconfigured converters and clients

[jira] [Updated] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-9228: - Fix Version/s: (was: 3.9.0) > Reconfigured converters and clients may not be propagated to

[jira] [Updated] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16837: -- Fix Version/s: (was: 3.9.0) > Kafka Connect fails on update connector for incorrect

[jira] [Updated] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16838: -- Fix Version/s: (was: 3.9.0) > Kafka Connect loads old tasks from removed connectors >

[jira] [Updated] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-9228: - Fix Version/s: 4.0.0 > Reconfigured converters and clients may not be propagated to connector

[jira] [Resolved] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-9228. -- Fix Version/s: 3.9.0 Resolution: Fixed > Reconfigured converters and clients may not be

[jira] [Updated] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16838: -- Fix Version/s: 3.7.1 > Kafka Connect loads old tasks from removed connectors >

[jira] [Updated] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16837: -- Fix Version/s: 3.7.1 > Kafka Connect fails on update connector for incorrect previous Config

[jira] [Updated] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16838: -- Fix Version/s: 3.8.0 > Kafka Connect loads old tasks from removed connectors >

[jira] [Updated] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16837: -- Fix Version/s: 3.8.0 > Kafka Connect fails on update connector for incorrect previous Config

[jira] [Resolved] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16838. --- Fix Version/s: 3.9.0 Resolution: Fixed > Kafka Connect loads old tasks from removed

[jira] [Resolved] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16837. --- Fix Version/s: 3.9.0 Resolution: Fixed > Kafka Connect fails on update connector for

[jira] [Assigned] (KAFKA-16881) InitialState type leaks into the Connect REST API OpenAPI spec

[ https://issues.apache.org/jira/browse/KAFKA-16881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-16881: - Assignee: 黃竣陽 > InitialState type leaks into the Connect REST API OpenAPI spec >

[jira] [Commented] (KAFKA-16881) InitialState type leaks into the Connect REST API OpenAPI spec

[ https://issues.apache.org/jira/browse/KAFKA-16881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851669#comment-17851669 ] Chris Egerton commented on KAFKA-16881: --- [~m1a2st] I've assigned the issue to you. Thanks for

[jira] [Commented] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851667#comment-17851667 ] Chris Egerton commented on KAFKA-16838: --- It's probably possible but it might get a bit messy. We'd

[jira] [Commented] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851129#comment-17851129 ] Chris Egerton commented on KAFKA-16838: --- I knew this one felt familiar–we actually fixed a more

[jira] [Resolved] (KAFKA-16844) ByteArrayConverter can't convert ByteBuffer

[ https://issues.apache.org/jira/browse/KAFKA-16844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16844. --- Fix Version/s: 3.8.0 Resolution: Fixed > ByteArrayConverter can't convert ByteBuffer

[jira] [Assigned] (KAFKA-16838) Kafka Connect loads old tasks from removed connectors

[ https://issues.apache.org/jira/browse/KAFKA-16838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-16838: - Assignee: Chris Egerton > Kafka Connect loads old tasks from removed connectors >

[jira] [Assigned] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-16837: - Assignee: Chris Egerton > Kafka Connect fails on update connector for incorrect

[jira] [Commented] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850059#comment-17850059 ] Chris Egerton commented on KAFKA-16837: --- Thanks for raising this [~mrMigles], great find! I don't

[jira] [Comment Edited] (KAFKA-16837) Kafka Connect fails on update connector for incorrect previous Config Provider tasks

[ https://issues.apache.org/jira/browse/KAFKA-16837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850059#comment-17850059 ] Chris Egerton edited comment on KAFKA-16837 at 5/28/24 3:07 PM: Thanks

[jira] [Assigned] (KAFKA-9228) Reconfigured converters and clients may not be propagated to connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-9228: Assignee: Chris Egerton (was: Greg Harris) > Reconfigured converters and clients may not

[jira] [Resolved] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16603. --- Resolution: Not A Bug > Data loss when kafka connect sending data to Kafka >

[jira] [Commented] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847880#comment-17847880 ] Chris Egerton commented on KAFKA-16603: --- Since this is not a bug (the Connect runtime does not

[jira] [Resolved] (KAFKA-16656) Using a custom replication.policy.separator with DefaultReplicationPolicy

[ https://issues.apache.org/jira/browse/KAFKA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16656. --- Resolution: Not A Bug > Using a custom replication.policy.separator with

[jira] [Commented] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846662#comment-17846662 ] Chris Egerton commented on KAFKA-16603: --- [~dasarianil] In most cases, a single worker-global

[jira] [Comment Edited] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845927#comment-17845927 ] Chris Egerton edited comment on KAFKA-16603 at 5/13/24 1:34 PM:

[jira] [Comment Edited] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845927#comment-17845927 ] Chris Egerton edited comment on KAFKA-16603 at 5/13/24 1:33 PM:

[jira] [Commented] (KAFKA-16603) Data loss when kafka connect sending data to Kafka

[ https://issues.apache.org/jira/browse/KAFKA-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845927#comment-17845927 ] Chris Egerton commented on KAFKA-16603: --- [~dasarianil] ah, nice! That takes advantage of existing

[jira] [Updated] (KAFKA-16445) PATCH method for connector configuration

[ https://issues.apache.org/jira/browse/KAFKA-16445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16445: -- Fix Version/s: 3.8.0 > PATCH method for connector configuration >

[jira] [Commented] (KAFKA-16656) Using a custom replication.policy.separator with DefaultReplicationPolicy

[ https://issues.apache.org/jira/browse/KAFKA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844653#comment-17844653 ] Chris Egerton commented on KAFKA-16656: --- Hmm... I've expanded this to an integration test to test

[jira] [Comment Edited] (KAFKA-16656) Using a custom replication.policy.separator with DefaultReplicationPolicy

[ https://issues.apache.org/jira/browse/KAFKA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844653#comment-17844653 ] Chris Egerton edited comment on KAFKA-16656 at 5/8/24 1:15 PM: --- Hmm...

[jira] [Resolved] (KAFKA-16108) Backport fix for KAFKA-16093 to 3.7

[ https://issues.apache.org/jira/browse/KAFKA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16108. --- Resolution: Done > Backport fix for KAFKA-16093 to 3.7 >

[jira] [Commented] (KAFKA-16108) Backport fix for KAFKA-16093 to 3.7

[ https://issues.apache.org/jira/browse/KAFKA-16108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844647#comment-17844647 ] Chris Egerton commented on KAFKA-16108: --- I set it to blocker as a reminder to backport before

[jira] [Resolved] (KAFKA-15018) Potential tombstone offsets corruption for exactly-once source connectors

[ https://issues.apache.org/jira/browse/KAFKA-15018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15018. --- Fix Version/s: 3.8.0 Resolution: Fixed > Potential tombstone offsets corruption for

[jira] [Commented] (KAFKA-16656) Using a custom replication.policy.separator with DefaultReplicationPolicy

[ https://issues.apache.org/jira/browse/KAFKA-16656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844368#comment-17844368 ] Chris Egerton commented on KAFKA-16656: --- Hi [~leninjoseph] it should be possible to use a custom

  1   2   3   4   5   6   7   8   9   10   >