[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&focusedCommentId=17856531#comment-17856531 ] Chris Egerton commented on KAFKA-16943: --- [~ksolves.kafka] the idea here isn't to a

[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 Egerto

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

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

[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&focusedCommentId=17855084#comment-17855084 ] Chris Egerton commented on KAFKA-10816: --- I've published [KIP-1017|https://cwiki.a

[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 t

[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 > InternalTo

[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 Projec

[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&focusedCommentId=17854113#comment-17854113 ] Chris Egerton commented on KAFKA-16931: --- Spoke too soon, have one more thought! [~

[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&focusedCommentId=17854091#comment-17854091 ] Chris Egerton edited comment on KAFKA-16931 at 6/11/24 3:09 PM: --

[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&focusedCommentId=17854091#comment-17854091 ] Chris Egerton edited comment on KAFKA-16931 at 6/11/24 3:06 PM: --

[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&focusedCommentId=17854091#comment-17854091 ] Chris Egerton commented on KAFKA-16931: --- First, one small clarification: task rest

[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 tas

[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 ma

[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 co

[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 previo

[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 tas

[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 c

[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&focusedCommentId=17851669#comment-17851669 ] Chris Egerton commented on KAFKA-16881: --- [~m1a2st] I've assigned the issue to you.

[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&focusedCommentId=17851667#comment-17851667 ] Chris Egerton commented on KAFKA-16838: --- It's probably possible but it might get a

[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&focusedCommentId=17851129#comment-17851129 ] Chris Egerton commented on KAFKA-16838: --- I knew this one felt familiar–we actually

[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 previou

[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&focusedCommentId=17850059#comment-17850059 ] Chris Egerton commented on KAFKA-16837: --- Thanks for raising this [~mrMigles], grea

[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&focusedCommentId=17850059#comment-17850059 ] Chris Egerton edited comment on KAFKA-16837 at 5/28/24 3:07 PM: --

[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&focusedCommentId=17847880#comment-17847880 ] Chris Egerton commented on KAFKA-16603: --- Since this is not a bug (the Connect runt

[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 DefaultReplicationP

[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&focusedCommentId=17846662#comment-17846662 ] Chris Egerton commented on KAFKA-16603: --- [~dasarianil] In most cases, a single wor

[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&focusedCommentId=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&focusedCommentId=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&focusedCommentId=17845927#comment-17845927 ] Chris Egerton commented on KAFKA-16603: --- [~dasarianil] ah, nice! That takes advant

[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&focusedCommentId=17844653#comment-17844653 ] Chris Egerton commented on KAFKA-16656: --- Hmm... I've expanded this to an integrati

[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&focusedCommentId=17844653#comment-17844653 ] Chris Egerton edited comment on KAFKA-16656 at 5/8/24 1:15 PM: ---

[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&focusedCommentId=17844647#comment-17844647 ] Chris Egerton commented on KAFKA-16108: --- I set it to blocker as a reminder to back

[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 e

[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&focusedCommentId=17844368#comment-17844368 ] Chris Egerton commented on KAFKA-16656: --- Hi [~leninjoseph] it should be possible t

[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 validatio

[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 validatio

[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&focusedCommentId=17842412#comment-17842412 ] Chris Egerton commented on KAFKA-16604: --- We don't necessarily have to deprecate an

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

[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&focusedCommentId=17842016#comment-17842016 ] Chris Egerton commented on KAFKA-16604: --- I don't know if it's worth the breaking c

[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) (w

[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 firs

[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 for

[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 > org.apache.kafka.connect.integration.OffsetsApi

[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 - > OffsetsApiIntegrationTest.testAlterSinkConnec

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

[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 t

[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&focusedCommentId=17810057#comment-17810057 ] Chris Egerton commented on KAFKA-15675: --- I've done some analysis on this one and b

[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 > ConnectorRestartApiIntegrationTest.testMultiWork

[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: Improvement

[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 pro

[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&focusedCommentId=17805158#comment-17805158 ] Chris Egerton commented on KAFKA-16093: --- Note that the "affects version(s)" field

[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&focusedCommentId=17804792#comment-17804792 ] Chris Egerton commented on KAFKA-16084: --- Thanks for the clarification [~gharris172

[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: https://issues.apache.org/jira/

[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&focusedCommentId=17803835#comment-17803835 ] Chris Egerton commented on KAFKA-16084: --- I don't think a mix of annotation- and me

[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 {{S

[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 {{S

[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&focusedCommentId=17795777#comment-17795777 ] Chris Egerton commented on KAFKA-15992: --- The heartbeats topic name is already conf

[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 Conn

[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 Issu

[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 b

[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&focusedCommentId=17794266#comment-17794266 ] Chris Egerton commented on KAFKA-15985: --- [~Reamer] Can you share your MM2 configur

[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&focusedCommentId=17792933#comment-17792933 ] Chris Egerton commented on KAFKA-15912: --- +1 for the concerns about lack of thread

[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&focusedCommentId=17792922#comment-17792922 ] Chris Egerton commented on KAFKA-10840: --- [~pnee] It's been a while but this does r

[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: Kafk

[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&focusedCommentId=17785147#comment-17785147 ] Chris Egerton commented on KAFKA-15575: --- I've published [KIP-1004|https://cwiki.a

[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 enume

[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 r

[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 > Partitio

[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&focusedCommentId=17783269#comment-17783269 ] Chris Egerton commented on KAFKA-15787: --- [~apoorvmittal10] please check for duplic

[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 > ConnectorRestartApiIntegrationTest.testMultiWorkerRestartOnlyConnect

[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&focusedCommentId=17781455#comment-17781455 ] Chris Egerton commented on KAFKA-15761: --- [~calvinliu] thanks for reporting this, b

[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 unnecessa

[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&focusedCommentId=17779977#comment-17779977 ] Chris Egerton commented on KAFKA-15693: --- For all affected versions, the most grace

[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: https://issues.apache.org/jira/browse/KAFK

[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 g

<    1   2   3   4   5   6   7   8   9   10   >