[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

[jira] [Resolved] (KAFKA-13329) Connect does not perform preflight validation for per-connector key and value converters

[ https://issues.apache.org/jira/browse/KAFKA-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13329. --- Fix Version/s: 3.8.0 Resolution: Fixed > Connect does not perform preflight

[jira] [Resolved] (KAFKA-13328) Connect does not perform preflight validation for per-connector header converters

[ https://issues.apache.org/jira/browse/KAFKA-13328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-13328. --- Fix Version/s: 3.8.0 Resolution: Fixed > Connect does not perform preflight

[jira] [Commented] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

[ https://issues.apache.org/jira/browse/KAFKA-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842412#comment-17842412 ] Chris Egerton commented on KAFKA-16604: --- We don't necessarily have to deprecate anything. It's a

[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=17842020#comment-17842020 ] Chris Egerton commented on KAFKA-16603: --- [~dasarianil] That's correct; {{Producer::send}} doesn't

[jira] [Commented] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

[ https://issues.apache.org/jira/browse/KAFKA-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842016#comment-17842016 ] Chris Egerton commented on KAFKA-16604: --- I don't know if it's worth the breaking change to

[jira] [Resolved] (KAFKA-16423) Ignoring offset partition key with an unexpected format for the first element in the partition key list. Expected type: java.lang.String, actual type: null"

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

[jira] [Resolved] (KAFKA-16423) Ignoring offset partition key with an unexpected format for the first element in the partition key list. Expected type: java.lang.String, actual type: null"

[ https://issues.apache.org/jira/browse/KAFKA-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-16423. --- Resolution: Duplicate > Ignoring offset partition key with an unexpected format for the

[jira] [Reopened] (KAFKA-16423) Ignoring offset partition key with an unexpected format for the first element in the partition key list. Expected type: java.lang.String, actual type: null"

[ https://issues.apache.org/jira/browse/KAFKA-16423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-16423: --- Assignee: (was: johndoe) > Ignoring offset partition key with an unexpected format

[jira] [Created] (KAFKA-16392) Spurious log warnings: "Ignoring offset partition key with an unexpected format for the second element in the partition key list. Expected type: java.util.Map, actual ty

Chris Egerton created KAFKA-16392: - Summary: Spurious log warnings: "Ignoring offset partition key with an unexpected format for the second element in the partition key list. Expected type: java.util.Map, actual type: null" Key:

[jira] [Resolved] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

[ https://issues.apache.org/jira/browse/KAFKA-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15575. --- Fix Version/s: 3.8.0 Resolution: Fixed > Prevent Connectors from exceeding tasks.max

[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: Chris Egerton > Flaky test >

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

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

[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=17811018#comment-17811018 ] Chris Egerton commented on KAFKA-10816: --- Hi [~tombentley], it's been a while since there's been

[jira] [Assigned] (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 reassigned KAFKA-10816: - Assignee: Chris Egerton (was: Tom Bentley) > Connect REST API should have a resource

[jira] [Commented] (KAFKA-15675) Fix flaky ConnectorRestartApiIntegrationTest.testMultiWorkerRestartOnlyConnector() test

[ https://issues.apache.org/jira/browse/KAFKA-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17810057#comment-17810057 ] Chris Egerton commented on KAFKA-15675: --- I've done some analysis on this one and believe I've

[jira] [Assigned] (KAFKA-15675) Fix flaky ConnectorRestartApiIntegrationTest.testMultiWorkerRestartOnlyConnector() test

[ https://issues.apache.org/jira/browse/KAFKA-15675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-15675: - Assignee: Chris Egerton > Fix flaky >

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

Chris Egerton created KAFKA-16108: - Summary: Backport fix for KAFKA-16093 to 3.7 Key: KAFKA-16108 URL: https://issues.apache.org/jira/browse/KAFKA-16108 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-16093) Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces

[ https://issues.apache.org/jira/browse/KAFKA-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16093: -- Fix Version/s: 3.6.2 > Spurious warnings logged to stderr about empty path annotations and

[jira] [Commented] (KAFKA-16093) Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces

[ https://issues.apache.org/jira/browse/KAFKA-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17805158#comment-17805158 ] Chris Egerton commented on KAFKA-16093: --- Note that the "affects version(s)" field is not

[jira] [Updated] (KAFKA-16093) Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces

[ https://issues.apache.org/jira/browse/KAFKA-16093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-16093: -- Affects Version/s: 3.6.1 3.6.0 3.6.2 > Spurious

[jira] [Commented] (KAFKA-16084) Simplify and deduplicate StandaloneHerderTest mocking

[ https://issues.apache.org/jira/browse/KAFKA-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17804792#comment-17804792 ] Chris Egerton commented on KAFKA-16084: --- Thanks for the clarification [~gharris1727], agree that

[jira] [Created] (KAFKA-16093) Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces

Chris Egerton created KAFKA-16093: - Summary: Spurious warnings logged to stderr about empty path annotations and providers not implementing provider interfaces Key: KAFKA-16093 URL:

[jira] [Commented] (KAFKA-16084) Simplify and deduplicate StandaloneHerderTest mocking

[ https://issues.apache.org/jira/browse/KAFKA-16084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17803835#comment-17803835 ] Chris Egerton commented on KAFKA-16084: --- I don't think a mix of annotation- and method-based mocks

[jira] [Updated] (KAFKA-15090) Source tasks are no longer stopped on a separate thread

[ https://issues.apache.org/jira/browse/KAFKA-15090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15090: -- Description: Before [https://github.com/apache/kafka/pull/9669], in distributed mode, the

[jira] [Updated] (KAFKA-15090) Source tasks are no longer stopped on a separate thread

[ https://issues.apache.org/jira/browse/KAFKA-15090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15090: -- Description: Before [https://github.com/apache/kafka/pull/9669], in distributed mode, the

[jira] [Commented] (KAFKA-15992) Make MM2 heartbeats topic name configurable

[ https://issues.apache.org/jira/browse/KAFKA-15992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795777#comment-17795777 ] Chris Egerton commented on KAFKA-15992: --- The heartbeats topic name is already configurable in

[jira] [Resolved] (KAFKA-15563) Provide informative error messages when Connect REST requests time out

[ https://issues.apache.org/jira/browse/KAFKA-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15563. --- Fix Version/s: 3.7.0 Resolution: Fixed > Provide informative error messages when

[jira] [Created] (KAFKA-15988) Kafka Connect OffsetsApiIntegrationTest takes too long

Chris Egerton created KAFKA-15988: - Summary: Kafka Connect OffsetsApiIntegrationTest takes too long Key: KAFKA-15988 URL: https://issues.apache.org/jira/browse/KAFKA-15988 Project: Kafka

[jira] [Updated] (KAFKA-14132) Remaining PowerMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-14132: -- Description: {color:#de350b}Some of the tests below use EasyMock as well. For those migrate

[jira] [Commented] (KAFKA-15985) Mirrormaker 2 offset sync is incomplete

[ https://issues.apache.org/jira/browse/KAFKA-15985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17794266#comment-17794266 ] Chris Egerton commented on KAFKA-15985: --- [~Reamer] Can you share your MM2 configuration (feel free

[jira] [Updated] (KAFKA-13988) Mirrormaker 2 auto.offset.reset=latest not working

[ https://issues.apache.org/jira/browse/KAFKA-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-13988: -- Fix Version/s: 3.6.2 > Mirrormaker 2 auto.offset.reset=latest not working >

[jira] [Commented] (KAFKA-15912) Parallelize conversion and transformation steps in Connect

[ https://issues.apache.org/jira/browse/KAFKA-15912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792933#comment-17792933 ] Chris Egerton commented on KAFKA-15912: --- +1 for the concerns about lack of thread safety in

[jira] [Commented] (KAFKA-10840) Need way to catch auth issues in poll method of Java Kafka client

[ https://issues.apache.org/jira/browse/KAFKA-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17792922#comment-17792922 ] Chris Egerton commented on KAFKA-10840: --- [~pnee] It's been a while but this does ring a bell. I

[jira] [Created] (KAFKA-15821) Active topics for deleted connectors are not reset in standalone mode

Chris Egerton created KAFKA-15821: - Summary: Active topics for deleted connectors are not reset in standalone mode Key: KAFKA-15821 URL: https://issues.apache.org/jira/browse/KAFKA-15821 Project:

[jira] [Commented] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

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

[jira] [Updated] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

[ https://issues.apache.org/jira/browse/KAFKA-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15575: -- Description: The Connector::taskConfigs(int maxTasks) function is used by Connectors to

[jira] [Updated] (KAFKA-15693) Disabling scheduled rebalance delay in Connect can lead to indefinitely unassigned connectors and tasks

[ https://issues.apache.org/jira/browse/KAFKA-15693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15693: -- Fix Version/s: 3.5.2 3.7.0 3.6.1 > Disabling scheduled

[jira] [Updated] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

[ https://issues.apache.org/jira/browse/KAFKA-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15575: -- Labels: kip (was: ) > Prevent Connectors from exceeding tasks.max configuration >

[jira] [Assigned] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

[ https://issues.apache.org/jira/browse/KAFKA-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-15575: - Assignee: Chris Egerton > Prevent Connectors from exceeding tasks.max configuration >

[jira] [Updated] (KAFKA-15680) Partition-Count is not getting updated Correctly in the Incremental Co-operative Rebalancing(ICR) Mode of Rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15680: -- Fix Version/s: 3.6.1 > Partition-Count is not getting updated Correctly in the Incremental >

[jira] [Resolved] (KAFKA-15680) Partition-Count is not getting updated Correctly in the Incremental Co-operative Rebalancing(ICR) Mode of Rebalancing

[ https://issues.apache.org/jira/browse/KAFKA-15680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15680. --- Fix Version/s: 3.7.0 (was: 3.6.1) Resolution: Fixed >

[jira] [Commented] (KAFKA-15787) Investigate new test case failure - testReplicateSourceDefault - MirrorConnectorsIntegrationBaseTest

[ https://issues.apache.org/jira/browse/KAFKA-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17783269#comment-17783269 ] Chris Egerton commented on KAFKA-15787: --- [~apoorvmittal10] please check for duplicates before

[jira] [Resolved] (KAFKA-15787) Investigate new test case failure - testReplicateSourceDefault - MirrorConnectorsIntegrationBaseTest

[ https://issues.apache.org/jira/browse/KAFKA-15787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15787. --- Resolution: Duplicate > Investigate new test case failure - testReplicateSourceDefault - >

[jira] [Resolved] (KAFKA-15761) ConnectorRestartApiIntegrationTest.testMultiWorkerRestartOnlyConnector is flaky

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

[jira] [Commented] (KAFKA-15761) ConnectorRestartApiIntegrationTest.testMultiWorkerRestartOnlyConnector is flaky

[ https://issues.apache.org/jira/browse/KAFKA-15761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781455#comment-17781455 ] Chris Egerton commented on KAFKA-15761: --- [~calvinliu] thanks for reporting this, but there's

[jira] [Assigned] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when group coordinator bounces

[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-15676: - Assignee: (was: Chris Egerton) > Scheduled rebalance delay for Connect is

[jira] [Commented] (KAFKA-15693) Disabling scheduled rebalance delay in Connect can lead to indefinitely unassigned connectors and tasks

[ https://issues.apache.org/jira/browse/KAFKA-15693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779977#comment-17779977 ] Chris Egerton commented on KAFKA-15693: --- For all affected versions, the most graceful workaround

[jira] [Created] (KAFKA-15693) Disabling scheduled rebalance delay in Connect can lead to indefinitely unassigned connectors and tasks

Chris Egerton created KAFKA-15693: - Summary: Disabling scheduled rebalance delay in Connect can lead to indefinitely unassigned connectors and tasks Key: KAFKA-15693 URL:

[jira] [Updated] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when group coordinator bounces

[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15676: -- Description: When a Connect worker loses contact with the group coordinator, it voluntarily

[jira] [Updated] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when group coordinator bounces

[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15676: -- Description: When a Connect worker loses contact with the group coordinator, it voluntarily

[jira] [Updated] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when group coordinator bounces

[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15676: -- Summary: Scheduled rebalance delay for Connect is unnecessarily triggered when group

[jira] [Commented] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when Kafka cluster bounces

[ https://issues.apache.org/jira/browse/KAFKA-15676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17779144#comment-17779144 ] Chris Egerton commented on KAFKA-15676: --- One possible fix for this is to simply wipe the state for

[jira] [Created] (KAFKA-15676) Scheduled rebalance delay for Connect is unnecessarily triggered when Kafka cluster bounces

Chris Egerton created KAFKA-15676: - Summary: Scheduled rebalance delay for Connect is unnecessarily triggered when Kafka cluster bounces Key: KAFKA-15676 URL: https://issues.apache.org/jira/browse/KAFKA-15676

[jira] [Resolved] (KAFKA-15428) Cluster-wide dynamic log adjustments for Connect

[ https://issues.apache.org/jira/browse/KAFKA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15428. --- Fix Version/s: 3.7.0 Resolution: Done > Cluster-wide dynamic log adjustments for

[jira] [Commented] (KAFKA-15575) Prevent Connectors from exceeding tasks.max configuration

[ https://issues.apache.org/jira/browse/KAFKA-15575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776849#comment-17776849 ] Chris Egerton commented on KAFKA-15575: --- I hate to say it, but I think this may need a KIP. I can

[jira] [Assigned] (KAFKA-13988) Mirrormaker 2 auto.offset.reset=latest not working

[ https://issues.apache.org/jira/browse/KAFKA-13988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-13988: - Assignee: Chris Egerton (was: Ravindranath Kakarla) > Mirrormaker 2

[jira] [Commented] (KAFKA-14132) Remaining PowerMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17776324#comment-17776324 ] Chris Egerton commented on KAFKA-14132: --- [~mdedetrich] I've unassigned the

[jira] [Updated] (KAFKA-14132) Remaining PowerMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-14132: -- Description: {color:#de350b}Some of the tests below use EasyMock as well. For those migrate

[jira] [Reopened] (KAFKA-15570) Add unit tests for MemoryConfigBackingStore

[ https://issues.apache.org/jira/browse/KAFKA-15570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reopened KAFKA-15570: --- > Add unit tests for MemoryConfigBackingStore > --- > >

[jira] [Resolved] (KAFKA-15570) Add unit tests for MemoryConfigBackingStore

[ https://issues.apache.org/jira/browse/KAFKA-15570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15570. --- Resolution: Done > Add unit tests for MemoryConfigBackingStore >

[jira] [Resolved] (KAFKA-15249) Verify Connect test-plugins artifact is published to Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15249. --- Resolution: Done > Verify Connect test-plugins artifact is published to Maven Central >

[jira] [Updated] (KAFKA-15428) Cluster-wide dynamic log adjustments for Connect

[ https://issues.apache.org/jira/browse/KAFKA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15428: -- Labels: kip (was: needs-kip) > Cluster-wide dynamic log adjustments for Connect >

[jira] [Created] (KAFKA-15563) Provide informative error messages when Connect REST requests time out

Chris Egerton created KAFKA-15563: - Summary: Provide informative error messages when Connect REST requests time out Key: KAFKA-15563 URL: https://issues.apache.org/jira/browse/KAFKA-15563 Project:

[jira] [Commented] (KAFKA-10339) MirrorMaker2 Exactly-once Semantics

[ https://issues.apache.org/jira/browse/KAFKA-10339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766887#comment-17766887 ] Chris Egerton commented on KAFKA-10339: --- There is no MirrorSinkConnector; we never implemented

[jira] [Resolved] (KAFKA-15473) Connect connector-plugins endpoint shows duplicate plugins

[ https://issues.apache.org/jira/browse/KAFKA-15473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-15473. --- Fix Version/s: 3.7.0 (was: 3.6.0) Resolution: Fixed > Connect

[jira] [Commented] (KAFKA-15249) Verify Connect test-plugins artifact is published to Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17763746#comment-17763746 ] Chris Egerton commented on KAFKA-15249: --- [~satish.duggana] I've added a note about this to

[jira] [Updated] (KAFKA-15249) Verify Connect test-plugins artifact is published to Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15249: -- Fix Version/s: (was: 3.6.0) > Verify Connect test-plugins artifact is published to Maven

[jira] [Updated] (KAFKA-15416) Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound

[ https://issues.apache.org/jira/browse/KAFKA-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15416: -- Fix Version/s: (was: 3.7.0) > Flaky test

[jira] [Updated] (KAFKA-15416) Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound

[ https://issues.apache.org/jira/browse/KAFKA-15416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15416: -- Fix Version/s: 3.6.0 > Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound

[jira] [Resolved] (KAFKA-15416) Flaky test TopicAdminTest::retryEndOffsetsShouldRetryWhenTopicNotFound

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

[jira] [Created] (KAFKA-15436) Custom ConfigDef validators are invoked with null when user-provided value does not match type

Chris Egerton created KAFKA-15436: - Summary: Custom ConfigDef validators are invoked with null when user-provided value does not match type Key: KAFKA-15436 URL: https://issues.apache.org/jira/browse/KAFKA-15436

[jira] [Comment Edited] (KAFKA-15249) Verify Connect test-plugins artifact is published to Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762088#comment-17762088 ] Chris Egerton edited comment on KAFKA-15249 at 9/5/23 1:29 PM: ---

[jira] [Commented] (KAFKA-15249) Verify Connect test-plugins artifact is published to Maven Central

[ https://issues.apache.org/jira/browse/KAFKA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17762088#comment-17762088 ] Chris Egerton commented on KAFKA-15249: --- [~satish.duggana] the ticket is a reminder to do checks

[jira] [Updated] (KAFKA-15428) Cluster-wide dynamic log adjustments for Connect

[ https://issues.apache.org/jira/browse/KAFKA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15428: -- Labels: needs-kip (was: Needs-kip) > Cluster-wide dynamic log adjustments for Connect >

[jira] [Updated] (KAFKA-15428) Cluster-wide dynamic log adjustments for Connect

[ https://issues.apache.org/jira/browse/KAFKA-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15428: -- Labels: Needs-kip (was: ) > Cluster-wide dynamic log adjustments for Connect >

[jira] [Created] (KAFKA-15428) Cluster-wide dynamic log adjustments for Connect

Chris Egerton created KAFKA-15428: - Summary: Cluster-wide dynamic log adjustments for Connect Key: KAFKA-15428 URL: https://issues.apache.org/jira/browse/KAFKA-15428 Project: Kafka Issue

[jira] [Updated] (KAFKA-15425) Compatibility break in Admin.listOffsets() (2)

[ https://issues.apache.org/jira/browse/KAFKA-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15425: -- Description: The behavioral change that warrants this ticket is identical to the change

[jira] [Updated] (KAFKA-15425) Compatibility break in Admin.listOffsets() (2)

[ https://issues.apache.org/jira/browse/KAFKA-15425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-15425: -- Description: The behavioral change that warrants this ticket is identical to the change

[jira] [Assigned] (KAFKA-14725) Improve cancellation semantics for connector tasks

[ https://issues.apache.org/jira/browse/KAFKA-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-14725: - Assignee: Chris Egerton (was: Yash Mayya) > Improve cancellation semantics for

[jira] [Comment Edited] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761097#comment-17761097 ] Chris Egerton edited comment on KAFKA-12879 at 8/31/23 10:20 PM: - Thanks

[jira] [Commented] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761097#comment-17761097 ] Chris Egerton commented on KAFKA-12879: --- Thanks Ismael. I've filed KAFKA-15425 to track the

[jira] [Assigned] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton reassigned KAFKA-12879: - Assignee: Philip Nee (was: Chris Egerton) > Compatibility break in

[jira] [Updated] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-12879: -- Affects Version/s: (was: 3.6.0) > Compatibility break in Admin.listOffsets() >

[jira] [Resolved] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton resolved KAFKA-12879. --- Resolution: Fixed > Compatibility break in Admin.listOffsets() >

[jira] [Updated] (KAFKA-12879) Compatibility break in Admin.listOffsets()

[ https://issues.apache.org/jira/browse/KAFKA-12879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Egerton updated KAFKA-12879: -- Fix Version/s: (was: 3.6.0) > Compatibility break in Admin.listOffsets() >

  1   2   3   4   5   6   7   8   9   10   >