[jira] [Updated] (KAFKA-16196) Cast transform doesn't handle invalid whole value casts gracefully

[ https://issues.apache.org/jira/browse/KAFKA-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-16196: --- Fix Version/s: 3.8.0 > Cast transform doesn't handle invalid whole value casts gracefully >

[jira] [Updated] (KAFKA-16196) Cast transform doesn't handle invalid whole value casts gracefully

[ https://issues.apache.org/jira/browse/KAFKA-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-16196: --- Description: The Cast transform currently doesn't handle invalid whole value casts gracefully. A

[jira] [Updated] (KAFKA-16196) Cast transform doesn't handle invalid whole value casts gracefully

[ https://issues.apache.org/jira/browse/KAFKA-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-16196: --- Description: The Cast transform currently doesn't handle invalid whole value casts gracefully. A

[jira] [Updated] (KAFKA-16196) Cast transform doesn't handle invalid whole value casts gracefully

[ https://issues.apache.org/jira/browse/KAFKA-16196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-16196: --- Description: The Cast transform currently doesn't handle invalid whole value casts gracefully. A

[jira] [Created] (KAFKA-16196) Cast transform doesn't handle invalid whole value casts gracefully

Yash Mayya created KAFKA-16196: -- Summary: Cast transform doesn't handle invalid whole value casts gracefully Key: KAFKA-16196 URL: https://issues.apache.org/jira/browse/KAFKA-16196 Project: Kafka

[jira] [Created] (KAFKA-15888) DistributedHerder log context should not use the same client ID for each Connect worker by default

Yash Mayya created KAFKA-15888: -- Summary: DistributedHerder log context should not use the same client ID for each Connect worker by default Key: KAFKA-15888 URL: https://issues.apache.org/jira/browse/KAFKA-15888

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

Yash Mayya created KAFKA-15570: -- Summary: Add unit tests for MemoryConfigBackingStore Key: KAFKA-15570 URL: https://issues.apache.org/jira/browse/KAFKA-15570 Project: Kafka Issue Type: Test

[jira] [Updated] (KAFKA-15547) Thread leak in MirrorMakerConfigTest#testClientConfigProperties

[ https://issues.apache.org/jira/browse/KAFKA-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15547: --- Issue Type: Test (was: Bug) > Thread leak in MirrorMakerConfigTest#testClientConfigProperties >

[jira] [Resolved] (KAFKA-15547) Thread leak in MirrorMakerConfigTest#testClientConfigProperties

[ https://issues.apache.org/jira/browse/KAFKA-15547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya resolved KAFKA-15547. Fix Version/s: 3.7.0 Resolution: Fixed > Thread leak in

[jira] [Resolved] (KAFKA-15177) MirrorMaker 2 should implement the alterOffsets KIP-875 API

[ https://issues.apache.org/jira/browse/KAFKA-15177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya resolved KAFKA-15177. Fix Version/s: 3.6.0 Resolution: Fixed > MirrorMaker 2 should implement the alterOffsets

[jira] [Updated] (KAFKA-15248) Add BooleanConverter to Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-15248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15248: --- Fix Version/s: 3.7.0 > Add BooleanConverter to Kafka Connect >

[jira] [Commented] (KAFKA-15470) Allow creating connectors in a stopped state

[ https://issues.apache.org/jira/browse/KAFKA-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17766107#comment-17766107 ] Yash Mayya commented on KAFKA-15470:

[jira] [Created] (KAFKA-15470) Allow creating connectors in a stopped state

Yash Mayya created KAFKA-15470: -- Summary: Allow creating connectors in a stopped state Key: KAFKA-15470 URL: https://issues.apache.org/jira/browse/KAFKA-15470 Project: Kafka Issue Type: New

[jira] [Resolved] (KAFKA-14067) Sink connector override.consumer.group.id can conflict with worker group.id

[ https://issues.apache.org/jira/browse/KAFKA-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya resolved KAFKA-14067. Resolution: Fixed > Sink connector override.consumer.group.id can conflict with worker group.id >

[jira] [Updated] (KAFKA-14067) Sink connector override.consumer.group.id can conflict with worker group.id

[ https://issues.apache.org/jira/browse/KAFKA-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14067: --- Fix Version/s: 3.7.0 > Sink connector override.consumer.group.id can conflict with worker group.id

[jira] [Commented] (KAFKA-14067) Sink connector override.consumer.group.id can conflict with worker group.id

[ https://issues.apache.org/jira/browse/KAFKA-14067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17764114#comment-17764114 ] Yash Mayya commented on KAFKA-14067: This has been fixed in

[jira] [Assigned] (KAFKA-14855) Harden integration testing logic for asserting that a connector is deleted

[ https://issues.apache.org/jira/browse/KAFKA-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-14855: -- Assignee: Yash Mayya > Harden integration testing logic for asserting that a connector is

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

[ https://issues.apache.org/jira/browse/KAFKA-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760929#comment-17760929 ] Yash Mayya commented on KAFKA-14725: [~ChrisEgerton] please feel free to take over this one, thanks. 

[jira] [Updated] (KAFKA-15387) Deprecate and remove Connect's redundant task configurations retrieval endpoint

[ https://issues.apache.org/jira/browse/KAFKA-15387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15387: --- Summary: Deprecate and remove Connect's redundant task configurations retrieval endpoint (was:

[jira] [Created] (KAFKA-15387) Deprecate and remove Connect's duplicate task configurations retrieval endpoint

Yash Mayya created KAFKA-15387: -- Summary: Deprecate and remove Connect's duplicate task configurations retrieval endpoint Key: KAFKA-15387 URL: https://issues.apache.org/jira/browse/KAFKA-15387 Project:

[jira] [Comment Edited] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756798#comment-17756798 ] Yash Mayya edited comment on KAFKA-15377 at 8/21/23 11:00 AM: -- Although I'd

[jira] [Comment Edited] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756798#comment-17756798 ] Yash Mayya edited comment on KAFKA-15377 at 8/21/23 11:00 AM: -- Although I'd

[jira] [Commented] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756798#comment-17756798 ] Yash Mayya commented on KAFKA-15377: Although I'd like to note that since the endpoint won't be

[jira] [Commented] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756797#comment-17756797 ] Yash Mayya commented on KAFKA-15377: Makes sense, thanks Mickael - I'll publish a small KIP soon. >

[jira] [Commented] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17756787#comment-17756787 ] Yash Mayya commented on KAFKA-15377: Yeah, we'd discussed this previously here -

[jira] [Comment Edited] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755826#comment-17755826 ] Yash Mayya edited comment on KAFKA-15377 at 8/18/23 7:13 AM: - [~mimaison]

[jira] [Commented] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755826#comment-17755826 ] Yash Mayya commented on KAFKA-15377: [~mimaison] [~ChrisEgerton] even though this does technically

[jira] [Updated] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

[ https://issues.apache.org/jira/browse/KAFKA-15377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15377: --- Description: The {{GET /connectors/\{connector}/tasks-config}} endpoint added in

[jira] [Created] (KAFKA-15377) GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values

Yash Mayya created KAFKA-15377: -- Summary: GET /connectors/{connector}/tasks-config endpoint exposes externalized secret values Key: KAFKA-15377 URL: https://issues.apache.org/jira/browse/KAFKA-15377

[jira] [Updated] (KAFKA-14133) Remaining EasyMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14133: --- Description: {color:#de350b}There are tests which use both PowerMock and EasyMock. I have put

[jira] [Updated] (KAFKA-14133) Remaining EasyMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14133: --- Description: {color:#de350b}There are tests which use both PowerMock and EasyMock. I have put

[jira] [Updated] (KAFKA-14133) Remaining EasyMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14133: --- Description: {color:#de350b}There are tests which use both PowerMock and EasyMock. I have put

[jira] [Updated] (KAFKA-14133) Remaining EasyMock to Mockito tests

[ https://issues.apache.org/jira/browse/KAFKA-14133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14133: --- Description: {color:#de350b}There are tests which use both PowerMock and EasyMock. I have put

[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 ] Yash Mayya updated KAFKA-14132: --- Description: {color:#de350b}Some of the tests below use EasyMock as well. For those migrate both

[jira] [Commented] (KAFKA-10457) JsonConverter.toConnectData trims BigInteger to Long for schema-less case

[ https://issues.apache.org/jira/browse/KAFKA-10457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17746865#comment-17746865 ] Yash Mayya commented on KAFKA-10457: If we want to add a new Connect schema type to accommodate big

[jira] (KAFKA-15238) Connect workers can be disabled by DLQ-related blocking admin client calls

[ https://issues.apache.org/jira/browse/KAFKA-15238 ] Yash Mayya deleted comment on KAFKA-15238: was (Author: yash.mayya): https://github.com/apache/kafka/pull/14079 > Connect workers can be disabled by DLQ-related blocking admin client calls

[jira] [Updated] (KAFKA-15238) Connect workers can be disabled by DLQ-related blocking admin client calls

[ https://issues.apache.org/jira/browse/KAFKA-15238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15238: --- Description: When Kafka Connect is run in distributed mode - if a sink connector's task is

[jira] [Updated] (KAFKA-15238) Connect workers can be disabled by DLQ-related blocking admin client calls

[ https://issues.apache.org/jira/browse/KAFKA-15238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15238: --- Summary: Connect workers can be disabled by DLQ-related blocking admin client calls (was: Connect

[jira] [Created] (KAFKA-15238) Connect workers can be disabled by DLQ related stuck admin client calls

Yash Mayya created KAFKA-15238: -- Summary: Connect workers can be disabled by DLQ related stuck admin client calls Key: KAFKA-15238 URL: https://issues.apache.org/jira/browse/KAFKA-15238 Project: Kafka

[jira] [Created] (KAFKA-15216) InternalSinkRecord::newRecord method ignores the headers argument

Yash Mayya created KAFKA-15216: -- Summary: InternalSinkRecord::newRecord method ignores the headers argument Key: KAFKA-15216 URL: https://issues.apache.org/jira/browse/KAFKA-15216 Project: Kafka

[jira] [Updated] (KAFKA-15182) Normalize offsets before invoking SourceConnector::alterOffsets

[ https://issues.apache.org/jira/browse/KAFKA-15182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15182: --- Description: See discussion

[jira] [Created] (KAFKA-15182) Normalize offsets before invoking SourceConnector::alterOffsets

Yash Mayya created KAFKA-15182: -- Summary: Normalize offsets before invoking SourceConnector::alterOffsets Key: KAFKA-15182 URL: https://issues.apache.org/jira/browse/KAFKA-15182 Project: Kafka

[jira] [Created] (KAFKA-15179) Add integration tests for the FileStream Sink and Source connectors

Yash Mayya created KAFKA-15179: -- Summary: Add integration tests for the FileStream Sink and Source connectors Key: KAFKA-15179 URL: https://issues.apache.org/jira/browse/KAFKA-15179 Project: Kafka

[jira] [Created] (KAFKA-15177) MirrorMaker 2 should implement the alterOffsets KIP-875 API

Yash Mayya created KAFKA-15177: -- Summary: MirrorMaker 2 should implement the alterOffsets KIP-875 API Key: KAFKA-15177 URL: https://issues.apache.org/jira/browse/KAFKA-15177 Project: Kafka

[jira] [Updated] (KAFKA-14353) Kafka Connect REST API configuration validation timeout improvements

[ https://issues.apache.org/jira/browse/KAFKA-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14353: --- Priority: Minor (was: Major) > Kafka Connect REST API configuration validation timeout

[jira] [Updated] (KAFKA-14353) Kafka Connect REST API configuration validation timeout improvements

[ https://issues.apache.org/jira/browse/KAFKA-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14353: --- Description: Kafka Connect currently defines a default REST API request timeout of [90

[jira] [Updated] (KAFKA-14353) Kafka Connect REST API configuration validation timeout improvements

[ https://issues.apache.org/jira/browse/KAFKA-14353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14353: --- Summary: Kafka Connect REST API configuration validation timeout improvements (was: Make Kafka

[jira] [Commented] (KAFKA-15151) Missing connector-stopped-task-count metric

[ https://issues.apache.org/jira/browse/KAFKA-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17740554#comment-17740554 ] Yash Mayya commented on KAFKA-15151: When a connector is stopped, all the tasks are shutdown - i.e.

[jira] [Assigned] (KAFKA-15151) Missing connector-stopped-task-count metric

[ https://issues.apache.org/jira/browse/KAFKA-15151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-15151: -- Assignee: Yash Mayya > Missing connector-stopped-task-count metric >

[jira] [Updated] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

[ https://issues.apache.org/jira/browse/KAFKA-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15145: --- Description: If a RetriableException is thrown from an admin client or producer client operation in

[jira] [Updated] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

[ https://issues.apache.org/jira/browse/KAFKA-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15145: --- Description: If a RetriableException is thrown from an admin client or producer client operation in

[jira] [Updated] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

[ https://issues.apache.org/jira/browse/KAFKA-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15145: --- Description: If a RetriableException is thrown from an admin client or producer client operation in

[jira] [Updated] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

[ https://issues.apache.org/jira/browse/KAFKA-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15145: --- Description: If a RetriableException is thrown from an admin client or producer client operation in

[jira] [Updated] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

[ https://issues.apache.org/jira/browse/KAFKA-15145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15145: --- Affects Version/s: 3.4.1 3.5.0 3.3.2

[jira] [Created] (KAFKA-15145) AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions

Yash Mayya created KAFKA-15145: -- Summary: AbstractWorkerSourceTask re-processes records filtered out by SMTs on retriable exceptions Key: KAFKA-15145 URL: https://issues.apache.org/jira/browse/KAFKA-15145

[jira] [Assigned] (KAFKA-15091) Javadocs for SourceTask::commit are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-15091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-15091: -- Assignee: Yash Mayya > Javadocs for SourceTask::commit are incorrect >

[jira] [Updated] (KAFKA-15121) FileStreamSourceConnector and FileStreamSinkConnector should implement KIP-875 APIs (alterOffsets)

[ https://issues.apache.org/jira/browse/KAFKA-15121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-15121: --- Summary: FileStreamSourceConnector and FileStreamSinkConnector should implement KIP-875 APIs

[jira] [Created] (KAFKA-15121) FileStreamSourceConnector and FileStreamSinkConnector should implement KIP-875 APIs

Yash Mayya created KAFKA-15121: -- Summary: FileStreamSourceConnector and FileStreamSinkConnector should implement KIP-875 APIs Key: KAFKA-15121 URL: https://issues.apache.org/jira/browse/KAFKA-15121

[jira] [Commented] (KAFKA-15113) Gracefully handle cases where a sink connector's admin and consumer client config overrides target different Kafka clusters

[ https://issues.apache.org/jira/browse/KAFKA-15113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17736483#comment-17736483 ] Yash Mayya commented on KAFKA-15113: Thanks for reviewing the ticket Chris! Yeah, I'm not sure

[jira] [Created] (KAFKA-15113) Gracefully handle cases where a sink connector's admin and consumer client config overrides target different Kafka clusters

Yash Mayya created KAFKA-15113: -- Summary: Gracefully handle cases where a sink connector's admin and consumer client config overrides target different Kafka clusters Key: KAFKA-15113 URL:

[jira] [Commented] (KAFKA-15091) Javadocs for SourceTask::commit are incorrect

[ https://issues.apache.org/jira/browse/KAFKA-15091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17732666#comment-17732666 ] Yash Mayya commented on KAFKA-15091: {quote}{{it does not have anything to do with the offsets

[jira] [Assigned] (KAFKA-15012) JsonConverter fails when there are leading Zeros in a field

[ https://issues.apache.org/jira/browse/KAFKA-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-15012: -- Assignee: Yash Mayya > JsonConverter fails when there are leading Zeros in a field >

[jira] [Comment Edited] (KAFKA-15012) JsonConverter fails when there are leading Zeros in a field

[ https://issues.apache.org/jira/browse/KAFKA-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725223#comment-17725223 ] Yash Mayya edited comment on KAFKA-15012 at 5/30/23 6:34 PM: - Thanks for

[jira] [Commented] (KAFKA-15012) JsonConverter fails when there are leading Zeros in a field

[ https://issues.apache.org/jira/browse/KAFKA-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727653#comment-17727653 ] Yash Mayya commented on KAFKA-15012: Thanks [~ChrisEgerton], that's a fair point. I was comparing

[jira] [Commented] (KAFKA-15034) Improvement of ReplaceField performance for long list

[ https://issues.apache.org/jira/browse/KAFKA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727119#comment-17727119 ] Yash Mayya commented on KAFKA-15034: Thanks for filing this ticket [~baz33]. I think what you're

[jira] [Assigned] (KAFKA-15034) Improvement of ReplaceField performance for long list

[ https://issues.apache.org/jira/browse/KAFKA-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-15034: -- Assignee: Yash Mayya > Improvement of ReplaceField performance for long list >

[jira] [Commented] (KAFKA-14956) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest#testGetSinkConnectorOffsetsDifferentKafkaClusterTargeted

[ https://issues.apache.org/jira/browse/KAFKA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727025#comment-17727025 ] Yash Mayya commented on KAFKA-14956: This test seems to be consistently passing after

[jira] [Resolved] (KAFKA-14956) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest#testGetSinkConnectorOffsetsDifferentKafkaClusterTargeted

[ https://issues.apache.org/jira/browse/KAFKA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya resolved KAFKA-14956. Resolution: Fixed > Flaky test >

[jira] [Commented] (KAFKA-14995) Automate asf.yaml collaborators refresh

[ https://issues.apache.org/jira/browse/KAFKA-14995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725722#comment-17725722 ] Yash Mayya commented on KAFKA-14995: [~dajac] that GitHub team isn't publicly accessible though.  

[jira] [Updated] (KAFKA-14952) Publish metrics when source connector fails to poll data

[ https://issues.apache.org/jira/browse/KAFKA-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14952: --- Labels: connect connect-api kip-required (was: connect connect-api) > Publish metrics when source

[jira] [Commented] (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:comment-tabpanel=17725713#comment-17725713 ] Yash Mayya commented on KAFKA-15018: Thanks for filing this bug ticket [~ChrisEgerton], it's an

[jira] [Commented] (KAFKA-15012) JsonConverter fails when there are leading Zeros in a field

[ https://issues.apache.org/jira/browse/KAFKA-15012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17725223#comment-17725223 ] Yash Mayya commented on KAFKA-15012: Thanks for filing this Jira [~ranjanrao]. Simply enabling the

[jira] [Commented] (KAFKA-14974) Restore backward compatibility in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-14974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17720566#comment-17720566 ] Yash Mayya commented on KAFKA-14974: Thanks [~rhauch], your understanding here is correct. We should

[jira] [Updated] (KAFKA-14455) Kafka Connect create and update REST APIs should surface failures while writing to the config topic

[ https://issues.apache.org/jira/browse/KAFKA-14455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14455: --- Fix Version/s: 3.5.0 3.4.1 3.3.3 > Kafka Connect create and

[jira] [Updated] (KAFKA-14974) Restore backward compatibility in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-14974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14974: --- Affects Version/s: 3.5.0 3.4.1 3.3.3 > Restore

[jira] [Created] (KAFKA-14974) Restore backward compatibility in KafkaBasedLog

Yash Mayya created KAFKA-14974: -- Summary: Restore backward compatibility in KafkaBasedLog Key: KAFKA-14974 URL: https://issues.apache.org/jira/browse/KAFKA-14974 Project: Kafka Issue Type: Task

[jira] [Updated] (KAFKA-14930) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14930: --- Description: Add public documentation for the new Kafka Connect offset management REST APIs from

[jira] [Assigned] (KAFKA-14956) Flaky test org.apache.kafka.connect.integration.OffsetsApiIntegrationTest#testGetSinkConnectorOffsetsDifferentKafkaClusterTargeted

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

[jira] [Commented] (KAFKA-14947) Duplicate records are getting created in the topic.

[ https://issues.apache.org/jira/browse/KAFKA-14947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718513#comment-17718513 ] Yash Mayya commented on KAFKA-14947: [~krishnendudas] the offset commits for source connectors were

[jira] [Updated] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs in 3.5

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14876: --- Description: Add public documentation for the new Kafka Connect REST APIs from

[jira] [Commented] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs in 3.5

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17718464#comment-17718464 ] Yash Mayya commented on KAFKA-14876: [~gharris1727] [~ChrisEgerton] sounds good, I've raised this PR

[jira] [Assigned] (KAFKA-13187) Replace EasyMock and PowerMock with Mockito for DistributedHerderTest

[ https://issues.apache.org/jira/browse/KAFKA-13187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-13187: -- Assignee: Yash Mayya (was: Matthew de Detrich) > Replace EasyMock and PowerMock with

[jira] [Comment Edited] (KAFKA-14947) Duplicate records are getting created in the topic.

[ https://issues.apache.org/jira/browse/KAFKA-14947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717095#comment-17717095 ] Yash Mayya edited comment on KAFKA-14947 at 4/27/23 9:58 AM: -

[jira] [Commented] (KAFKA-14947) Duplicate records are getting created in the topic.

[ https://issues.apache.org/jira/browse/KAFKA-14947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17717095#comment-17717095 ] Yash Mayya commented on KAFKA-14947: [~krishnendudas] this seems like a bug in the connector's

[jira] [Created] (KAFKA-14933) Document Kafka Connect's log level REST APIs added in KIP-495

Yash Mayya created KAFKA-14933: -- Summary: Document Kafka Connect's log level REST APIs added in KIP-495 Key: KAFKA-14933 URL: https://issues.apache.org/jira/browse/KAFKA-14933 Project: Kafka

[jira] [Updated] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs in 3.5

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14876: --- Description: Add public documentation for the new Kafka Connect offset management REST API being

[jira] [Updated] (KAFKA-14930) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14930: --- Description: Add public documentation for the 3 new Kafka Connect offset management REST APIs

[jira] [Assigned] (KAFKA-14930) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-14930: -- Assignee: Yash Mayya > Public documentation for new Kafka Connect offset management REST

[jira] [Updated] (KAFKA-14930) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14930: --- Fix Version/s: 3.6.0 > Public documentation for new Kafka Connect offset management REST APIs >

[jira] [Commented] (KAFKA-14923) Upgrade io.netty_netty-codec for CVE-2022-41881

[ https://issues.apache.org/jira/browse/KAFKA-14923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714541#comment-17714541 ] Yash Mayya commented on KAFKA-14923: [~vikashmishra0808] looks like

[jira] [Comment Edited] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713158#comment-17713158 ] Yash Mayya edited comment on KAFKA-14876 at 4/17/23 4:11 PM: - Yep, makes

[jira] [Commented] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713183#comment-17713183 ] Yash Mayya commented on KAFKA-14876: [~ChrisEgerton] I think we should document the new stop API

[jira] [Commented] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs

[ https://issues.apache.org/jira/browse/KAFKA-14876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17713158#comment-17713158 ] Yash Mayya commented on KAFKA-14876: Yep, makes sense, I can raise a PR for that tomorrow. > Public

[jira] [Created] (KAFKA-14910) Consider cancelling ongoing alter connector offsets requests when the connector is resumed

Yash Mayya created KAFKA-14910: -- Summary: Consider cancelling ongoing alter connector offsets requests when the connector is resumed Key: KAFKA-14910 URL: https://issues.apache.org/jira/browse/KAFKA-14910

[jira] [Updated] (KAFKA-14910) Consider cancelling ongoing alter / reset connector offsets requests when the connector is resumed

[ https://issues.apache.org/jira/browse/KAFKA-14910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya updated KAFKA-14910: --- Summary: Consider cancelling ongoing alter / reset connector offsets requests when the connector is

[jira] [Assigned] (KAFKA-14858) Standalone herder does not handle exceptions thrown from connector taskConfigs method

[ https://issues.apache.org/jira/browse/KAFKA-14858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yash Mayya reassigned KAFKA-14858: -- Assignee: Yash Mayya > Standalone herder does not handle exceptions thrown from connector >

[jira] [Commented] (KAFKA-14746) Throwing in Connector.taskConfigs in distributed mode generates a lot of logs

[ https://issues.apache.org/jira/browse/KAFKA-14746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17709965#comment-17709965 ] Yash Mayya commented on KAFKA-14746: I agree that the intent of the retries seems to be mainly to

[jira] [Created] (KAFKA-14876) Public documentation for new Kafka Connect offset management REST APIs

Yash Mayya created KAFKA-14876: -- Summary: Public documentation for new Kafka Connect offset management REST APIs Key: KAFKA-14876 URL: https://issues.apache.org/jira/browse/KAFKA-14876 Project: Kafka

[jira] [Created] (KAFKA-14844) Kafka Connect's OffsetBackingStore interface should handle (de)serialization and connector namespacing

Yash Mayya created KAFKA-14844: -- Summary: Kafka Connect's OffsetBackingStore interface should handle (de)serialization and connector namespacing Key: KAFKA-14844 URL:

[jira] [Commented] (KAFKA-14814) Skip restart of connectors when redundant resume request is made

[ https://issues.apache.org/jira/browse/KAFKA-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17703107#comment-17703107 ] Yash Mayya commented on KAFKA-14814: Hi [~cmukka20], I've re-assigned the ticket to you! Feel free

  1   2   >