[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 ] Randall Hauch updated KAFKA-14974: -- Fix Version/s: 3.5.0 > Restore backward compatibility in KafkaBasedLog > -

[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 ] Randall Hauch updated KAFKA-14974: -- Fix Version/s: 3.4.1 3.3.3 > Restore backward compatibility in KafkaBasedLo

[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 ] Randall Hauch updated KAFKA-14974: -- Fix Version/s: 3.6.0 > Restore backward compatibility in KafkaBasedLog > -

[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&focusedCommentId=17720553#comment-17720553 ] Randall Hauch commented on KAFKA-14974: --- [~yash.mayya], just to clarify: # #12984

[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 ] Randall Hauch updated KAFKA-14974: -- Component/s: KafkaConnect > Restore backward compatibility in KafkaBasedLog >

[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&focusedCommentId=17720546#comment-17720546 ] Randall Hauch commented on KAFKA-14974: --- Thanks for catching this and providing a

[jira] [Commented] (KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"

[ https://issues.apache.org/jira/browse/KAFKA-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17571601#comment-17571601 ] Randall Hauch commented on KAFKA-14079: --- Merged to the `3.3` branch with permissio

[jira] [Updated] (KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"

[ https://issues.apache.org/jira/browse/KAFKA-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-14079: -- Fix Version/s: 3.4.0 > Source task will not commit offsets and develops memory leak if > "err

[jira] [Commented] (KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"

[ https://issues.apache.org/jira/browse/KAFKA-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568626#comment-17568626 ] Randall Hauch commented on KAFKA-14079: --- Following up with some additional detail:

[jira] [Resolved] (KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"

[ https://issues.apache.org/jira/browse/KAFKA-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-14079. --- Reviewer: Randall Hauch Resolution: Fixed > Source task will not commit offsets and de

[jira] [Updated] (KAFKA-14079) Source task will not commit offsets and develops memory leak if "error.tolerance" is set to "all"

[ https://issues.apache.org/jira/browse/KAFKA-14079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-14079: -- Priority: Critical (was: Major) > Source task will not commit offsets and develops memory lea

[jira] [Resolved] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-13770. --- Reviewer: Konstantine Karantasis Resolution: Fixed > Regression when Connect uses 0.10

[jira] [Updated] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13770: -- Fix Version/s: (was: 2.5.2) > Regression when Connect uses 0.10.x brokers due to recently

[jira] [Commented] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512192#comment-17512192 ] Randall Hauch commented on KAFKA-13770: --- Merged the changes to `trunk` after the P

[jira] [Updated] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13770: -- Description: KAFKA-12879 recently modified Connect's `KafkaBasedLog` class to add retry logic

[jira] [Assigned] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-13770: - Assignee: Randall Hauch > Regression when Connect uses 0.10.x brokers due to recently a

[jira] [Updated] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

[ https://issues.apache.org/jira/browse/KAFKA-13770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13770: -- Description: KAFKA-12879 recently modified Connect's `KafkaBasedLog` class to add retry logic

[jira] [Created] (KAFKA-13770) Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog

Randall Hauch created KAFKA-13770: - Summary: Regression when Connect uses 0.10.x brokers due to recently added retry logic in KafkaBasedLog Key: KAFKA-13770 URL: https://issues.apache.org/jira/browse/KAFKA-13770

[jira] [Assigned] (KAFKA-7509) Kafka Connect logs unnecessary warnings about unused configurations

[ https://issues.apache.org/jira/browse/KAFKA-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-7509: Assignee: (was: Randall Hauch) > Kafka Connect logs unnecessary warnings about unused

[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&focusedCommentId=17504584#comment-17504584 ] Randall Hauch edited comment on KAFKA-12879 at 3/10/22, 9:22 PM: -

[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 ] Randall Hauch resolved KAFKA-12879. --- Reviewer: Randall Hauch 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 ] Randall Hauch updated KAFKA-12879: -- Fix Version/s: 3.2.0 > 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 ] Randall Hauch updated KAFKA-12879: -- Fix Version/s: 3.0.2 2.7.3 2.6.4 2.5.2

[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&focusedCommentId=17504584#comment-17504584 ] Randall Hauch commented on KAFKA-12879: --- Update: I'm having trouble with backporti

[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&focusedCommentId=17503891#comment-17503891 ] Randall Hauch edited comment on KAFKA-12879 at 3/10/22, 9:13 PM: -

[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&focusedCommentId=17503891#comment-17503891 ] Randall Hauch commented on KAFKA-12879: --- The approach we decided to take was to re

[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&focusedCommentId=17481998#comment-17481998 ] Randall Hauch edited comment on KAFKA-12879 at 1/25/22, 5:52 PM: -

[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&focusedCommentId=17481998#comment-17481998 ] Randall Hauch commented on KAFKA-12879: --- The original intent of [KAFKA-12339|http

[jira] [Updated] (KAFKA-13469) End-of-life offset commit for source task can take place before all records are flushed

[ https://issues.apache.org/jira/browse/KAFKA-13469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13469: -- Fix Version/s: 3.2.0 > End-of-life offset commit for source task can take place before all rec

[jira] [Comment Edited] (KAFKA-13370) Offset commit failure percentage metric is not computed correctly (regression)

[ https://issues.apache.org/jira/browse/KAFKA-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444638#comment-17444638 ] Randall Hauch edited comment on KAFKA-13370 at 11/16/21, 5:01 PM:

[jira] [Commented] (KAFKA-13370) Offset commit failure percentage metric is not computed correctly (regression)

[ https://issues.apache.org/jira/browse/KAFKA-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444638#comment-17444638 ] Randall Hauch commented on KAFKA-13370: --- I reverted the change (https://github.com

[jira] [Updated] (KAFKA-13370) Offset commit failure percentage metric is not computed correctly (regression)

[ https://issues.apache.org/jira/browse/KAFKA-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13370: -- Fix Version/s: 2.8.2 > Offset commit failure percentage metric is not computed correctly (regr

[jira] [Comment Edited] (KAFKA-13370) Offset commit failure percentage metric is not computed correctly (regression)

[ https://issues.apache.org/jira/browse/KAFKA-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444615#comment-17444615 ] Randall Hauch edited comment on KAFKA-13370 at 11/16/21, 3:47 PM:

[jira] [Commented] (KAFKA-13370) Offset commit failure percentage metric is not computed correctly (regression)

[ https://issues.apache.org/jira/browse/KAFKA-13370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17444615#comment-17444615 ] Randall Hauch commented on KAFKA-13370: --- Thanks, [~showuon], creating the PR that

[jira] [Updated] (KAFKA-12226) High-throughput source tasks fail to commit offsets

[ https://issues.apache.org/jira/browse/KAFKA-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12226: -- Fix Version/s: 3.0.1 3.2.0 > High-throughput source tasks fail to commit of

[jira] [Commented] (KAFKA-12226) High-throughput source tasks fail to commit offsets

[ https://issues.apache.org/jira/browse/KAFKA-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17443975#comment-17443975 ] Randall Hauch commented on KAFKA-12226: --- Thanks for catching this, [~dajac]. I did

[jira] [Commented] (KAFKA-12226) High-throughput source tasks fail to commit offsets

[ https://issues.apache.org/jira/browse/KAFKA-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440067#comment-17440067 ] Randall Hauch commented on KAFKA-12226: --- Merged the PR to the `trunk` branch, whic

[jira] [Updated] (KAFKA-12226) High-throughput source tasks fail to commit offsets

[ https://issues.apache.org/jira/browse/KAFKA-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12226: -- Fix Version/s: 3.1.0 > High-throughput source tasks fail to commit offsets > -

[jira] [Commented] (KAFKA-9887) failed-task-count JMX metric not updated if task fails during startup

[ https://issues.apache.org/jira/browse/KAFKA-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435681#comment-17435681 ] Randall Hauch commented on KAFKA-9887: -- Backported to the `3.0` branch, so it will b

[jira] [Updated] (KAFKA-9887) failed-task-count JMX metric not updated if task fails during startup

[ https://issues.apache.org/jira/browse/KAFKA-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-9887: - Fix Version/s: 3.0.1 > failed-task-count JMX metric not updated if task fails during startup > --

[jira] [Resolved] (KAFKA-13118) Backport KAFKA-9887 to 3.0 branch after 3.0.0 release

[ https://issues.apache.org/jira/browse/KAFKA-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-13118. --- Resolution: Fixed Backported to the `3.0` branch. Will be in the 3.0.1 release. > Backport

[jira] [Assigned] (KAFKA-10865) Improve trace-logging for Transformations (including Predicates)

[ https://issues.apache.org/jira/browse/KAFKA-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-10865: - Assignee: Tiago Martins (was: Govinda Sakhare) > Improve trace-logging for Transformat

[jira] [Updated] (KAFKA-10865) Improve trace-logging for Transformations (including Predicates)

[ https://issues.apache.org/jira/browse/KAFKA-10865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10865: -- [~upsidedownsmile], I've assigned this issue to you as requested. You are now listed as a contrib

[jira] [Commented] (KAFKA-2376) Add Kafka Connect metrics

[ https://issues.apache.org/jira/browse/KAFKA-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389959#comment-17389959 ] Randall Hauch commented on KAFKA-2376: -- [~ramkrish1489], it's not uncommon for a KIP

[jira] [Commented] (KAFKA-10627) Connect TimestampConverter transform does not support multiple formats for the same field and only allows one field to be transformed at a time

[ https://issues.apache.org/jira/browse/KAFKA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388779#comment-17388779 ] Randall Hauch commented on KAFKA-10627: --- Thanks, [~joshuagrisham]! I've added you

[jira] [Assigned] (KAFKA-10627) Connect TimestampConverter transform does not support multiple formats for the same field and only allows one field to be transformed at a time

[ https://issues.apache.org/jira/browse/KAFKA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-10627: - Assignee: Joshua Grisham > Connect TimestampConverter transform does not support multip

[jira] [Updated] (KAFKA-10627) Connect TimestampConverter transform does not support multiple formats for the same field and only allows one field to be transformed at a time

[ https://issues.apache.org/jira/browse/KAFKA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10627: -- Issue Type: New Feature (was: Improvement) > Connect TimestampConverter transform does not su

[jira] [Updated] (KAFKA-10627) Connect TimestampConverter transform does not support multiple formats for the same field and only allows one field to be transformed at a time

[ https://issues.apache.org/jira/browse/KAFKA-10627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10627: -- Labels: connect-transformation need-kip (was: ) > Connect TimestampConverter transform does n

[jira] [Commented] (KAFKA-13139) Empty response after requesting to restart a connector without the tasks results in NPE

[ https://issues.apache.org/jira/browse/KAFKA-13139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388116#comment-17388116 ] Randall Hauch commented on KAFKA-13139: --- Just to clarify what appears to have happ

[jira] [Updated] (KAFKA-13118) Backport KAFKA-9887 to 3.0 branch after 3.0.0 release

[ https://issues.apache.org/jira/browse/KAFKA-13118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-13118: -- Description: We need to backport the fix (commit hash `0314801a8e`) for KAFKA-9887 to the `3.

[jira] [Created] (KAFKA-13118) Backport KAFKA-9887 to 3.0 branch after 3.0.0 release

Randall Hauch created KAFKA-13118: - Summary: Backport KAFKA-9887 to 3.0 branch after 3.0.0 release Key: KAFKA-13118 URL: https://issues.apache.org/jira/browse/KAFKA-13118 Project: Kafka Issue

[jira] [Commented] (KAFKA-9887) failed-task-count JMX metric not updated if task fails during startup

[ https://issues.apache.org/jira/browse/KAFKA-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385005#comment-17385005 ] Randall Hauch commented on KAFKA-9887: -- Unfortunately, the 3.0 code freeze was two w

[jira] [Resolved] (KAFKA-13035) Kafka Connect: Update documentation for POST /connectors/(string: name)/restart to include task Restart behavior

[ https://issues.apache.org/jira/browse/KAFKA-13035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-13035. --- Fix Version/s: 3.0.0 Reviewer: Randall Hauch Resolution: Fixed Merged to `tr

[jira] [Assigned] (KAFKA-13028) AbstractConfig should allow config provider configuration to use variables referencing other config providers earlier in the list

[ https://issues.apache.org/jira/browse/KAFKA-13028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-13028: - Assignee: Randall Hauch > AbstractConfig should allow config provider configuration to

[jira] [Commented] (KAFKA-13028) AbstractConfig should allow config provider configuration to use variables referencing other config providers earlier in the list

[ https://issues.apache.org/jira/browse/KAFKA-13028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373715#comment-17373715 ] Randall Hauch commented on KAFKA-13028: --- h2. Is a KIP required? [KIP-421|https://c

[jira] [Created] (KAFKA-13028) AbstractConfig should allow config provider configuration to use variables referencing other config providers earlier in the list

Randall Hauch created KAFKA-13028: - Summary: AbstractConfig should allow config provider configuration to use variables referencing other config providers earlier in the list Key: KAFKA-13028 URL: https://issues.a

[jira] [Resolved] (KAFKA-12717) Remove internal converter config properties

[ https://issues.apache.org/jira/browse/KAFKA-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12717. --- Reviewer: Randall Hauch Resolution: Fixed Merged to the `trunk` branch for 3.0.0. > R

[jira] [Resolved] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12482. --- Reviewer: Randall Hauch Resolution: Fixed Merged to `trunk`. > Remove deprecated rest

[jira] [Resolved] (KAFKA-12484) Enable Connect's connector log contexts by default

[ https://issues.apache.org/jira/browse/KAFKA-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12484. --- Reviewer: Konstantine Karantasis Resolution: Fixed Merged to the `trunk` branch for in

[jira] [Resolved] (KAFKA-12483) Enable client overrides in connector configs by default

[ https://issues.apache.org/jira/browse/KAFKA-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12483. --- Resolution: Fixed Merged to the `trunk` branch for inclusion in 3.0.0. > Enable client over

[jira] [Commented] (KAFKA-12252) Distributed herder tick thread loops rapidly when worker loses leadership

[ https://issues.apache.org/jira/browse/KAFKA-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17365610#comment-17365610 ] Randall Hauch commented on KAFKA-12252: --- Backported to 2.6 for inclusion in any su

[jira] [Updated] (KAFKA-12252) Distributed herder tick thread loops rapidly when worker loses leadership

[ https://issues.apache.org/jira/browse/KAFKA-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12252: -- Fix Version/s: 2.6.3 > Distributed herder tick thread loops rapidly when worker loses leadersh

[jira] [Updated] (KAFKA-12252) Distributed herder tick thread loops rapidly when worker loses leadership

[ https://issues.apache.org/jira/browse/KAFKA-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12252: -- Fix Version/s: 2.7.2 Backported to 2.7 for inclusion in any subsequent 2.7.2 patch release. >

[jira] [Commented] (KAFKA-12483) Enable client overrides in connector configs by default

[ https://issues.apache.org/jira/browse/KAFKA-12483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358864#comment-17358864 ] Randall Hauch commented on KAFKA-12483: --- KIP-722 was approved today. > Enable cli

[jira] [Commented] (KAFKA-12484) Enable Connect's connector log contexts by default

[ https://issues.apache.org/jira/browse/KAFKA-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358860#comment-17358860 ] Randall Hauch commented on KAFKA-12484: --- KIP-721 was approved today. > Enable Con

[jira] [Updated] (KAFKA-12904) Connect's validate REST endpoint uses incorrect timeout

[ https://issues.apache.org/jira/browse/KAFKA-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12904: -- Description: The fix for KAFKA-9374 changed how the `ConnectorPluginsResource` and its method

[jira] [Updated] (KAFKA-12904) Connect's validate REST endpoint uses incorrect timeout

[ https://issues.apache.org/jira/browse/KAFKA-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12904: -- Description: The fix for KAFKA-9374 changed how the `ConnectorPluginsResource` and its method

[jira] [Commented] (KAFKA-9374) Worker can be disabled by blocked connectors

[ https://issues.apache.org/jira/browse/KAFKA-9374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358713#comment-17358713 ] Randall Hauch commented on KAFKA-9374: -- Please ignore link to [GitHub Pull Request

[jira] [Assigned] (KAFKA-12904) Connect's validate REST endpoint uses incorrect timeout

[ https://issues.apache.org/jira/browse/KAFKA-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-12904: - Assignee: Randall Hauch > Connect's validate REST endpoint uses incorrect timeout > ---

[jira] [Updated] (KAFKA-12904) Connect's validate REST endpoint uses incorrect timeout

[ https://issues.apache.org/jira/browse/KAFKA-12904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12904: -- Description: The fix for KAFKA-9374 changed how the `ConnectorPluginsResource` and its method

[jira] [Created] (KAFKA-12904) Connect's validate REST endpoint uses incorrect timeout

Randall Hauch created KAFKA-12904: - Summary: Connect's validate REST endpoint uses incorrect timeout Key: KAFKA-12904 URL: https://issues.apache.org/jira/browse/KAFKA-12904 Project: Kafka Iss

[jira] [Assigned] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-12482: - Assignee: Kalpesh Patel > Remove deprecated rest.host.name and rest.port Connect worker

[jira] [Commented] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17356530#comment-17356530 ] Randall Hauch commented on KAFKA-12482: --- Update: it's time to remove these -- it's

[jira] [Updated] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12482: -- Description: The following Connect worker configuration properties were deprecated and should

[jira] [Updated] (KAFKA-12717) Remove internal converter config properties

[ https://issues.apache.org/jira/browse/KAFKA-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12717: -- Issue Type: Task (was: Bug) > Remove internal converter config properties > -

[jira] [Updated] (KAFKA-12717) Remove internal converter config properties

[ https://issues.apache.org/jira/browse/KAFKA-12717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12717: -- Fix Version/s: 3.0.0 > Remove internal converter config properties > -

[jira] [Updated] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12482: -- Issue Type: Task (was: Improvement) > Remove deprecated rest.host.name and rest.port Connect

[jira] [Updated] (KAFKA-12482) Remove deprecated rest.host.name and rest.port Connect worker configs

[ https://issues.apache.org/jira/browse/KAFKA-12482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12482: -- Summary: Remove deprecated rest.host.name and rest.port Connect worker configs (was: Remove d

[jira] [Commented] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355973#comment-17355973 ] Randall Hauch commented on KAFKA-4793: -- [~kpatelatwork], thanks for offering. Yes, y

[jira] [Commented] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355860#comment-17355860 ] Randall Hauch commented on KAFKA-4793: -- I've created a KIP that expands the existing

[jira] [Commented] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17355287#comment-17355287 ] Randall Hauch commented on KAFKA-4793: -- I'm picking this up, and will add a KIP that

[jira] [Resolved] (KAFKA-7749) confluent does not provide option to set consumer properties at connector level

[ https://issues.apache.org/jira/browse/KAFKA-7749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-7749. -- Fix Version/s: 2.3.0 Resolution: Fixed [KIP-458|https://cwiki.apache.org/confluence/disp

[jira] [Assigned] (KAFKA-4793) Kafka Connect: POST /connectors/(string: name)/restart doesn't start failed tasks

[ https://issues.apache.org/jira/browse/KAFKA-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-4793: Assignee: Randall Hauch > Kafka Connect: POST /connectors/(string: name)/restart doesn't s

[jira] [Commented] (KAFKA-5892) Connector property override does not work unless setting ALL converter properties

[ https://issues.apache.org/jira/browse/KAFKA-5892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352737#comment-17352737 ] Randall Hauch commented on KAFKA-5892: -- [~dc-heros], I've added your account as a co

[jira] [Resolved] (KAFKA-12252) Distributed herder tick thread loops rapidly when worker loses leadership

[ https://issues.apache.org/jira/browse/KAFKA-12252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-12252. --- Fix Version/s: 2.8.1 3.0.0 Resolution: Fixed I'm still working on

[jira] [Commented] (KAFKA-10340) Source connectors should report error when trying to produce records to non-existent topics instead of hanging forever

[ https://issues.apache.org/jira/browse/KAFKA-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17339862#comment-17339862 ] Randall Hauch commented on KAFKA-10340: --- I cherry-picked the original PR (https://

[jira] [Updated] (KAFKA-10340) Source connectors should report error when trying to produce records to non-existent topics instead of hanging forever

[ https://issues.apache.org/jira/browse/KAFKA-10340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10340: -- Fix Version/s: 2.8.1 > Source connectors should report error when trying to produce records to

[jira] [Updated] (KAFKA-10231) Broken Kafka Connect node to node communication if invalid hostname is in place

[ https://issues.apache.org/jira/browse/KAFKA-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10231: -- Description: As a Kafka Connect operator I would expect a more definitive error when the inte

[jira] [Updated] (KAFKA-10231) Broken Kafka Connect node to node communication if invalid hostname is in place

[ https://issues.apache.org/jira/browse/KAFKA-10231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-10231: -- Description: As a Kafka Connect operator I would expect a more definitive error when the inte

[jira] [Updated] (KAFKA-6985) Error connection between cluster node

[ https://issues.apache.org/jira/browse/KAFKA-6985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6985: - Component/s: (was: KafkaConnect) core > Error connection between cluster nod

[jira] [Resolved] (KAFKA-8551) Comments for connectors() in Herder interface

[ https://issues.apache.org/jira/browse/KAFKA-8551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8551. -- Resolution: Won't Fix Marking as won't fix, since the details are insufficient to try to addres

[jira] [Resolved] (KAFKA-8664) non-JSON format messages when streaming data from Kafka to Mongo

[ https://issues.apache.org/jira/browse/KAFKA-8664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8664. -- Resolution: Won't Fix The reported problem is for a connector implementation that is not owned

[jira] [Resolved] (KAFKA-8867) Kafka Connect JDBC fails to create PostgreSQL table with default boolean value in schema

[ https://issues.apache.org/jira/browse/KAFKA-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8867. -- Resolution: Won't Fix The reported problem is for the Confluent JDBC source/sink connector, and

[jira] [Resolved] (KAFKA-8961) Unable to create secure JDBC connection through Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-8961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8961. -- Resolution: Won't Fix This is not a problem of the Connect framework, and is instead an issue w

[jira] [Updated] (KAFKA-9017) We see timeout in kafka in production cluster

[ https://issues.apache.org/jira/browse/KAFKA-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-9017: - Component/s: (was: KafkaConnect) core > We see timeout in kafka in productio

[jira] [Commented] (KAFKA-10715) Support Kafka connect converter for AVRO

[ https://issues.apache.org/jira/browse/KAFKA-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17315110#comment-17315110 ] Randall Hauch commented on KAFKA-10715: --- There are multiple Converter implementati

[jira] [Resolved] (KAFKA-10715) Support Kafka connect converter for AVRO

[ https://issues.apache.org/jira/browse/KAFKA-10715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-10715. --- Resolution: Won't Do > Support Kafka connect converter for AVRO > --

[jira] [Updated] (KAFKA-9988) Connect incorrectly logs that task has failed when one takes too long to shutdown

[ https://issues.apache.org/jira/browse/KAFKA-9988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-9988: - Labels: newbie (was: ) > Connect incorrectly logs that task has failed when one takes too long t

[jira] [Commented] (KAFKA-12474) Worker can die if unable to write new session key

[ https://issues.apache.org/jira/browse/KAFKA-12474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313476#comment-17313476 ] Randall Hauch commented on KAFKA-12474: --- Merged to the `trunk` branch after the `2

[jira] [Updated] (KAFKA-12474) Worker can die if unable to write new session key

[ https://issues.apache.org/jira/browse/KAFKA-12474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-12474: -- Fix Version/s: 2.8.0 > Worker can die if unable to write new session key > ---

  1   2   3   4   5   6   7   8   9   10   >