[jira] [Assigned] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-6252: Assignee: Arjun Satish > A metric named 'XX' already exists, can't register another one. >

[jira] [Commented] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309852#comment-16309852 ] Randall Hauch commented on KAFKA-6252: -- As for how we might more gracefully deal with

[jira] [Comment Edited] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309815#comment-16309815 ] Randall Hauch edited comment on KAFKA-6252 at 1/3/18 4:05 PM: --

[jira] [Commented] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309815#comment-16309815 ] Randall Hauch commented on KAFKA-6252: -- As mentioned above, connectors run into this

[jira] [Commented] (KAFKA-6417) plugin.path pointing at a plugin directory causes ClassNotFoundException

[ https://issues.apache.org/jira/browse/KAFKA-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16308451#comment-16308451 ] Randall Hauch commented on KAFKA-6417: -- We should definitely improve the documentatio

[jira] [Updated] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6142: - Description: Currently, when a worker or connector configuration is parsed, the values are used a

[jira] [Updated] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6142: - Description: Currently, when a worker or connector configuration is parsed, the values are used a

[jira] [Commented] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300204#comment-16300204 ] Randall Hauch commented on KAFKA-6142: -- This proposal doesn't explicitly address pass

[jira] [Commented] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300193#comment-16300193 ] Randall Hauch commented on KAFKA-6142: -- It should be possible to have an empty string

[jira] [Created] (KAFKA-6387) Worker's producer and consumer configs should inherit from worker configs

Randall Hauch created KAFKA-6387: Summary: Worker's producer and consumer configs should inherit from worker configs Key: KAFKA-6387 URL: https://issues.apache.org/jira/browse/KAFKA-6387 Project: Kafk

[jira] [Commented] (KAFKA-6353) Connector status shows FAILED but actually task is in RUNNING status

[ https://issues.apache.org/jira/browse/KAFKA-6353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295315#comment-16295315 ] Randall Hauch commented on KAFKA-6353: -- [~airbots], per https://kafka.apache.org/cont

[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291750#comment-16291750 ] Randall Hauch commented on KAFKA-3821: -- [~gunnar.morling], no, there is no KIP for th

[jira] [Commented] (KAFKA-6311) Expose Kafka cluster ID in Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291735#comment-16291735 ] Randall Hauch commented on KAFKA-6311: -- And KIP is available here: https://cwiki.apa

[jira] [Commented] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291119#comment-16291119 ] Randall Hauch commented on KAFKA-6252: -- No, I don't think there are any workarounds,

[jira] [Commented] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286021#comment-16286021 ] Randall Hauch commented on KAFKA-5117: -- BTW, the KIP doesn't have to be that complex,

[jira] [Commented] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286014#comment-16286014 ] Randall Hauch commented on KAFKA-5117: -- This issue is requesting a change in a public

[jira] [Updated] (KAFKA-5117) Kafka Connect REST endpoints reveal Password typed values

[ https://issues.apache.org/jira/browse/KAFKA-5117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5117: - Labels: needs-kip (was: ) > Kafka Connect REST endpoints reveal Password typed values > -

[jira] [Assigned] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-6313: Assignee: Randall Hauch (was: Ismael Juma) > Kafka Core maven dependencies are missing SLF

[jira] [Updated] (KAFKA-6311) Expose Kafka cluster ID in Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6311: - Labels: needs-kip (was: ) > Expose Kafka cluster ID in Connect REST API > ---

[jira] [Comment Edited] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280260#comment-16280260 ] Randall Hauch edited comment on KAFKA-6313 at 12/6/17 2:50 PM: -

[jira] [Comment Edited] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280260#comment-16280260 ] Randall Hauch edited comment on KAFKA-6313 at 12/6/17 2:50 PM: -

[jira] [Commented] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

[ https://issues.apache.org/jira/browse/KAFKA-6313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280260#comment-16280260 ] Randall Hauch commented on KAFKA-6313: -- [~ijuma], you are correct that other dependen

[jira] [Created] (KAFKA-6313) Kafka Core maven dependencies are missing SLF4J API

Randall Hauch created KAFKA-6313: Summary: Kafka Core maven dependencies are missing SLF4J API Key: KAFKA-6313 URL: https://issues.apache.org/jira/browse/KAFKA-6313 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6252: - Description: When a connector crashes (or is not implemented correctly by not stopping/interrupti

[jira] [Updated] (KAFKA-6290) Kafka Connect cast transformation should support logical types

[ https://issues.apache.org/jira/browse/KAFKA-6290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6290: - Labels: confluent-kafka confluentic connect connect-api connect-transformation kafka kafka-con

[jira] [Updated] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6252: - Priority: Critical (was: Major) > A metric named 'XX' already exists, can't register another one.

[jira] [Commented] (KAFKA-6252) A metric named 'XX' already exists, can't register another one.

[ https://issues.apache.org/jira/browse/KAFKA-6252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269781#comment-16269781 ] Randall Hauch commented on KAFKA-6252: -- This also happens when a connector does not p

[jira] [Resolved] (KAFKA-6279) Connect metrics do not get cleaned up for a source connector that doesn't stop properly

[ https://issues.apache.org/jira/browse/KAFKA-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6279. -- Resolution: Duplicate > Connect metrics do not get cleaned up for a source connector that doesn'

[jira] [Commented] (KAFKA-6279) Connect metrics do not get cleaned up for a source connector that doesn't stop properly

[ https://issues.apache.org/jira/browse/KAFKA-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269776#comment-16269776 ] Randall Hauch commented on KAFKA-6279: -- This was recently reported as KAFKA-6252, so

[jira] [Updated] (KAFKA-6279) Connect metrics do not get cleaned up for a source connector that doesn't stop properly

[ https://issues.apache.org/jira/browse/KAFKA-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6279: - Priority: Critical (was: Major) > Connect metrics do not get cleaned up for a source connector th

[jira] [Created] (KAFKA-6279) Connect metrics do not get cleaned up for a source connector that doesn't stop properly

Randall Hauch created KAFKA-6279: Summary: Connect metrics do not get cleaned up for a source connector that doesn't stop properly Key: KAFKA-6279 URL: https://issues.apache.org/jira/browse/KAFKA-6279

[jira] [Commented] (KAFKA-4107) Support offset reset capability in Kafka Connect

[ https://issues.apache.org/jira/browse/KAFKA-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16258502#comment-16258502 ] Randall Hauch commented on KAFKA-4107: -- [~Satyajit], that would be great. However, t

[jira] [Commented] (KAFKA-4115) Grow default heap settings for distributed Connect from 256M to 1G

[ https://issues.apache.org/jira/browse/KAFKA-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252713#comment-16252713 ] Randall Hauch commented on KAFKA-4115: -- The {{kafka-run-class.sh}} current [sets the

[jira] [Updated] (KAFKA-5967) Ineffective check of negative value in CompositeReadOnlyKeyValueStore#approximateNumEntries()

[ https://issues.apache.org/jira/browse/KAFKA-5967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5967: - Component/s: streams > Ineffective check of negative value in > CompositeReadOnlyKeyValueStore#ap

[jira] [Created] (KAFKA-6208) Reduce startup time for Kafka Connect workers

Randall Hauch created KAFKA-6208: Summary: Reduce startup time for Kafka Connect workers Key: KAFKA-6208 URL: https://issues.apache.org/jira/browse/KAFKA-6208 Project: Kafka Issue Type: Impro

[jira] [Created] (KAFKA-6201) Provide more context in Kafka Connect REST error messages

Randall Hauch created KAFKA-6201: Summary: Provide more context in Kafka Connect REST error messages Key: KAFKA-6201 URL: https://issues.apache.org/jira/browse/KAFKA-6201 Project: Kafka Issue

[jira] [Comment Edited] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247654#comment-16247654 ] Randall Hauch edited comment on KAFKA-4827 at 11/10/17 3:40 PM:

[jira] [Updated] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4827: - Fix Version/s: 0.11.0.3 > Kafka connect: error with special characters in connector name > ---

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247654#comment-16247654 ] Randall Hauch commented on KAFKA-4827: -- [~sliebau], I re-added {{0.10.1.2}} and {{0.1

[jira] [Updated] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4827: - Fix Version/s: 0.10.2.2 0.10.1.2 > Kafka connect: error with special characters

[jira] [Commented] (KAFKA-6007) Connect can't validate against transforms in plugins.path

[ https://issues.apache.org/jira/browse/KAFKA-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16247634#comment-16247634 ] Randall Hauch commented on KAFKA-6007: -- [~rsivaram], can you create a `0.11.0.3` rele

[jira] [Updated] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4827: - Fix Version/s: 1.1.0 0.11.0.2 0.10.2.2 0.1

[jira] [Commented] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246637#comment-16246637 ] Randall Hauch commented on KAFKA-4827: -- This actually doesn't have anything to do wit

[jira] [Issue Comment Deleted] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4827: - Comment: was deleted (was: To be clear, connector names should be *URL-encoded* in the REST reques

[jira] [Issue Comment Deleted] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4827: - Comment: was deleted (was: I'm closing this issue, since KAFKA-4930 is actually closer to the hear

[jira] [Reopened] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-4827: -- > Kafka connect: error with special characters in connector name > -

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch edited comment on KAFKA-4930 at 11/9/17 8:39 PM: -

[jira] [Resolved] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4827. -- Resolution: Won't Fix To be clear, connector names should be *URL-encoded* in the REST request a

[jira] [Reopened] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-4827: -- > Kafka connect: error with special characters in connector name > -

[jira] [Resolved] (KAFKA-4827) Kafka connect: error with special characters in connector name

[ https://issues.apache.org/jira/browse/KAFKA-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4827. -- Resolution: Fixed I'm closing this issue, since KAFKA-4930 is actually closer to the heart of th

[jira] [Resolved] (KAFKA-4938) Creating a connector with missing name parameter throws a NullPointerException

[ https://issues.apache.org/jira/browse/KAFKA-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4938. -- Resolution: Duplicate I'm closing this issue, since KAFKA-4930 is actually closer to the heart o

[jira] [Reopened] (KAFKA-5669) Define allowed characters for connector names

[ https://issues.apache.org/jira/browse/KAFKA-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reopened KAFKA-5669: -- > Define allowed characters for connector names > - > >

[jira] [Resolved] (KAFKA-5669) Define allowed characters for connector names

[ https://issues.apache.org/jira/browse/KAFKA-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5669. -- Resolution: Duplicate > Define allowed characters for connector names >

[jira] [Resolved] (KAFKA-5669) Define allowed characters for connector names

[ https://issues.apache.org/jira/browse/KAFKA-5669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5669. -- Resolution: Won't Fix I'm closing this issue, since KAFKA-4930 is actually closer to the heart o

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch edited comment on KAFKA-4930 at 11/9/17 8:27 PM: -

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch edited comment on KAFKA-4930 at 11/9/17 8:27 PM: -

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch edited comment on KAFKA-4930 at 11/9/17 8:27 PM: -

[jira] [Comment Edited] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch edited comment on KAFKA-4930 at 11/9/17 8:26 PM: -

[jira] [Commented] (KAFKA-4930) Connect Rest API allows creating connectors with an empty name

[ https://issues.apache.org/jira/browse/KAFKA-4930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16246460#comment-16246460 ] Randall Hauch commented on KAFKA-4930: -- [~sliebau] created KIP-212 and then started t

[jira] [Commented] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238698#comment-16238698 ] Randall Hauch commented on KAFKA-6168: -- [~yuzhih...@gmail.com], thanks for offering t

[jira] [Assigned] (KAFKA-6168) Connect Schema comparison is slow for large schemas

[ https://issues.apache.org/jira/browse/KAFKA-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-6168: Assignee: Ted Yu > Connect Schema comparison is slow for large schemas > --

[jira] [Created] (KAFKA-6168) Connect Schema comparison is slow for large schemas

Randall Hauch created KAFKA-6168: Summary: Connect Schema comparison is slow for large schemas Key: KAFKA-6168 URL: https://issues.apache.org/jira/browse/KAFKA-6168 Project: Kafka Issue Type:

[jira] [Updated] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

[ https://issues.apache.org/jira/browse/KAFKA-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6142: - Description: Currently, when a worker or connector configuration is parsed, the values are used a

[jira] [Created] (KAFKA-6142) Connect worker configurations and connector configurations should accept environment variables

Randall Hauch created KAFKA-6142: Summary: Connect worker configurations and connector configurations should accept environment variables Key: KAFKA-6142 URL: https://issues.apache.org/jira/browse/KAFKA-6142

[jira] [Commented] (KAFKA-6133) NullPointerException in S3 Connector when using rotate.interval.ms

[ https://issues.apache.org/jira/browse/KAFKA-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222945#comment-16222945 ] Randall Hauch commented on KAFKA-6133: -- No worries, [~zzbennett]. Just cleaning up a

[jira] [Closed] (KAFKA-6133) NullPointerException in S3 Connector when using rotate.interval.ms

[ https://issues.apache.org/jira/browse/KAFKA-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch closed KAFKA-6133. > NullPointerException in S3 Connector when using rotate.interval.ms > -

[jira] [Resolved] (KAFKA-6133) NullPointerException in S3 Connector when using rotate.interval.ms

[ https://issues.apache.org/jira/browse/KAFKA-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-6133. -- Resolution: Invalid Closing this as INVALID, since this is not Apache Kafka code. These connect

[jira] [Resolved] (KAFKA-4575) Transient failure in ConnectDistributedTest.test_pause_and_resume_sink in consuming messages after resuming sink connector

[ https://issues.apache.org/jira/browse/KAFKA-4575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-4575. -- Resolution: Fixed This appears to no longer be an issue, so I'm closing this as fixed. > Transi

[jira] [Commented] (KAFKA-6007) Connect can't validate against transforms in plugins.path

[ https://issues.apache.org/jira/browse/KAFKA-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16199478#comment-16199478 ] Randall Hauch commented on KAFKA-6007: -- [~kkonstantine], thanks for the excellent dia

[jira] [Updated] (KAFKA-6007) Connect can't validate against transforms in plugins.path

[ https://issues.apache.org/jira/browse/KAFKA-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-6007: - Fix Version/s: (was: 0.10.0.2) 0.11.0.2 > Connect can't validate against tr

[jira] [Commented] (KAFKA-5295) Allow Kafka Connect source connectors to specify topic-specific settings for new topics

[ https://issues.apache.org/jira/browse/KAFKA-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197744#comment-16197744 ] Randall Hauch commented on KAFKA-5295: -- [~mageshn], that would be great! Assigned to

[jira] [Assigned] (KAFKA-5295) Allow Kafka Connect source connectors to specify topic-specific settings for new topics

[ https://issues.apache.org/jira/browse/KAFKA-5295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch reassigned KAFKA-5295: Assignee: Magesh kumar Nandakumar > Allow Kafka Connect source connectors to specify topic-

[jira] [Resolved] (KAFKA-5774) WorkerSinkTask failure exception should include cause

[ https://issues.apache.org/jira/browse/KAFKA-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5774. -- Resolution: Fixed Fix Version/s: 1.0.0 Indeed, this was [fixed with this PR|https://githu

[jira] [Commented] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194885#comment-16194885 ] Randall Hauch commented on KAFKA-4794: -- [~olkuznsmith], when I said the connector can

[jira] [Updated] (KAFKA-3821) Allow Kafka Connect source tasks to produce offset without writing to topics

[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-3821: - Fix Version/s: 1.1.0 > Allow Kafka Connect source tasks to produce offset without writing to topic

[jira] [Commented] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194806#comment-16194806 ] Randall Hauch commented on KAFKA-4794: -- This KIP didn't get enough votes to make it i

[jira] [Updated] (KAFKA-4794) Add access to OffsetStorageReader from SourceConnector

[ https://issues.apache.org/jira/browse/KAFKA-4794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-4794: - Fix Version/s: 1.1.0 > Add access to OffsetStorageReader from SourceConnector > --

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

[ https://issues.apache.org/jira/browse/KAFKA-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-2376. -- Resolution: Fixed All of the subtasks have been completed, so marking this as fixed. > Add Kafk

[jira] [Resolved] (KAFKA-5904) Create Connect metrics for worker rebalances

[ https://issues.apache.org/jira/browse/KAFKA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-5904. -- Resolution: Fixed Resolved as part of the [PR](https://github.com/apache/kafka/pull/4011) for K

[jira] [Commented] (KAFKA-5953) Connect classloader isolation may be broken for JDBC drivers

[ https://issues.apache.org/jira/browse/KAFKA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193156#comment-16193156 ] Randall Hauch commented on KAFKA-5953: -- No, that's not the source of the problem. It

[jira] [Issue Comment Deleted] (KAFKA-5953) Connect classloader isolation may be broken for JDBC drivers

[ https://issues.apache.org/jira/browse/KAFKA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5953: - Comment: was deleted (was: A potential workaround is to put all of the JDBC driver JARs on the cl

[jira] [Commented] (KAFKA-5953) Connect classloader isolation may be broken for JDBC drivers

[ https://issues.apache.org/jira/browse/KAFKA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192183#comment-16192183 ] Randall Hauch commented on KAFKA-5953: -- A potential workaround is to put all of the J

[jira] [Comment Edited] (KAFKA-5953) Connect classloader isolation may be broken for JDBC drivers

[ https://issues.apache.org/jira/browse/KAFKA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16192183#comment-16192183 ] Randall Hauch edited comment on KAFKA-5953 at 10/4/17 11:07 PM:

[jira] [Commented] (KAFKA-5953) Connect classloader isolation may be broken for JDBC drivers

[ https://issues.apache.org/jira/browse/KAFKA-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191824#comment-16191824 ] Randall Hauch commented on KAFKA-5953: -- [~jpechane] wrote: {quote} As a result a Dri

[jira] [Updated] (KAFKA-5987) Kafka metrics templates used in document generation should maintain order of tags

[ https://issues.apache.org/jira/browse/KAFKA-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5987: - Fix Version/s: (was: 1.0.0) 1.0.1 > Kafka metrics templates used in documen

[jira] [Commented] (KAFKA-5904) Create Connect metrics for worker rebalances

[ https://issues.apache.org/jira/browse/KAFKA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16190826#comment-16190826 ] Randall Hauch commented on KAFKA-5904: -- The changes for this issue were included in t

[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=16188311#comment-16188311 ] Randall Hauch commented on KAFKA-2376: -- [~guozhang], yes, they will be completed in t

[jira] [Created] (KAFKA-5990) Add generated documentation for Connect metrics

Randall Hauch created KAFKA-5990: Summary: Add generated documentation for Connect metrics Key: KAFKA-5990 URL: https://issues.apache.org/jira/browse/KAFKA-5990 Project: Kafka Issue Type: Sub

[jira] [Created] (KAFKA-5987) Kafka metrics templates used in document generation should maintain order of tags

Randall Hauch created KAFKA-5987: Summary: Kafka metrics templates used in document generation should maintain order of tags Key: KAFKA-5987 URL: https://issues.apache.org/jira/browse/KAFKA-5987 Proje

[jira] [Commented] (KAFKA-4632) Kafka Connect WorkerSinkTask.closePartitions doesn't handle WakeupException

[ https://issues.apache.org/jira/browse/KAFKA-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182785#comment-16182785 ] Randall Hauch commented on KAFKA-4632: -- Actually, it looks like at least as far back

[jira] [Commented] (KAFKA-4632) Kafka Connect WorkerSinkTask.closePartitions doesn't handle WakeupException

[ https://issues.apache.org/jira/browse/KAFKA-4632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182770#comment-16182770 ] Randall Hauch commented on KAFKA-4632: -- [~ScottReynolds], thanks for reporting this.

[jira] [Updated] (KAFKA-5902) Create Connect metrics for sink tasks

[ https://issues.apache.org/jira/browse/KAFKA-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5902: - Fix Version/s: (was: 1.1.0) 1.0.0 > Create Connect metrics for sink tasks >

[jira] [Updated] (KAFKA-5904) Create Connect metrics for worker rebalances

[ https://issues.apache.org/jira/browse/KAFKA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5904: - Fix Version/s: (was: 1.1.0) 1.0.0 > Create Connect metrics for worker rebal

[jira] [Updated] (KAFKA-5903) Create Connect metrics for workers

[ https://issues.apache.org/jira/browse/KAFKA-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5903: - Fix Version/s: (was: 1.1.0) 1.0.0 > Create Connect metrics for workers > --

[jira] [Updated] (KAFKA-5901) Create Connect metrics for source tasks

[ https://issues.apache.org/jira/browse/KAFKA-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5901: - Fix Version/s: (was: 1.1.0) 1.0.0 > Create Connect metrics for source tasks

[jira] [Updated] (KAFKA-5900) Create Connect metrics common to source and sink tasks

[ https://issues.apache.org/jira/browse/KAFKA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5900: - Fix Version/s: (was: 1.1.0) 1.0.0 > Create Connect metrics common to source

[jira] [Commented] (KAFKA-5900) Create Connect metrics common to source and sink tasks

[ https://issues.apache.org/jira/browse/KAFKA-5900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179855#comment-16179855 ] Randall Hauch commented on KAFKA-5900: -- Not sure why, but the [PR for this issue|htt

[jira] [Updated] (KAFKA-5904) Create Connect metrics for worker rebalances

[ https://issues.apache.org/jira/browse/KAFKA-5904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5904: - Priority: Blocker (was: Critical) > Create Connect metrics for worker rebalances > --

[jira] [Updated] (KAFKA-5903) Create Connect metrics for workers

[ https://issues.apache.org/jira/browse/KAFKA-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5903: - Priority: Blocker (was: Critical) > Create Connect metrics for workers >

[jira] [Updated] (KAFKA-5902) Create Connect metrics for sink tasks

[ https://issues.apache.org/jira/browse/KAFKA-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch updated KAFKA-5902: - Priority: Blocker (was: Critical) > Create Connect metrics for sink tasks > -

<    5   6   7   8   9   10   11   >