[jira] [Commented] (KAFKA-5568) Transformations that mutate topic-partitions break sink connectors that manage their own configuration

[ https://issues.apache.org/jira/browse/KAFKA-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16078385#comment-16078385 ] Ewen Cheslack-Postava commented on KAFKA-5568: -- Yeah, I probably should have given more of an

[jira] [Resolved] (KAFKA-5579) SchemaBuilder.type(Schema.Type) should not allow null.

[ https://issues.apache.org/jira/browse/KAFKA-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5579. -- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-5608) System test failure due to timeout starting Jmx tool

[ https://issues.apache.org/jira/browse/KAFKA-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092467#comment-16092467 ] Ewen Cheslack-Postava commented on KAFKA-5608: -- Another interesting point by [~hachikuji] is

[jira] [Resolved] (KAFKA-5623) ducktape kafka service: do not assume Service contains num_nodes

[ https://issues.apache.org/jira/browse/KAFKA-5623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5623. -- Resolution: Fixed Fix Version/s: 0.11.0.1 0.10.2.2

[jira] [Assigned] (KAFKA-5468) Change Source offset commit message to info to match Sink behaviour

[ https://issues.apache.org/jira/browse/KAFKA-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5468: Assignee: Stephane Maarek Reviewer: Ewen Cheslack-Postava > Change

[jira] [Commented] (KAFKA-5505) Connect: Do not restart connector and existing tasks on task-set change

[ https://issues.apache.org/jira/browse/KAFKA-5505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095747#comment-16095747 ] Ewen Cheslack-Postava commented on KAFKA-5505: -- There's been some discussion about more

[jira] [Commented] (KAFKA-5563) Clarify handling of connector name in config

[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095722#comment-16095722 ] Ewen Cheslack-Postava commented on KAFKA-5563: -- [~sliebau] I think validation that they match

[jira] [Assigned] (KAFKA-5535) Transformations - tranformations for value broken on tombstone events

[ https://issues.apache.org/jira/browse/KAFKA-5535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5535: Assignee: Ewen Cheslack-Postava > Transformations - tranformations for

[jira] [Commented] (KAFKA-5000) Framework should log some progress information regularly to assist in troubleshooting

[ https://issues.apache.org/jira/browse/KAFKA-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095830#comment-16095830 ] Ewen Cheslack-Postava commented on KAFKA-5000: -- Should this be logs or just covered by the

[jira] [Assigned] (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:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-4930: Assignee: Sönke Liebau > Connect Rest API allows creating connectors with

[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=16095792#comment-16095792 ] Ewen Cheslack-Postava commented on KAFKA-4827: -- [~sliebau] Yeah, naming is, unfortunately,

[jira] [Commented] (KAFKA-5067) java.sql.SQLDataException on TimeStamp column when using AWS Redshift as a JDBC source

[ https://issues.apache.org/jira/browse/KAFKA-5067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095854#comment-16095854 ] Ewen Cheslack-Postava commented on KAFKA-5067: -- This also looks like it has more to do with

[jira] [Commented] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16095825#comment-16095825 ] Ewen Cheslack-Postava commented on KAFKA-4915: -- [~dernasherbrezon] Can you clarify the

[jira] [Resolved] (KAFKA-5089) JAR mismatch in KafkaConnect leads to NoSuchMethodError in HDP 2.6

[ https://issues.apache.org/jira/browse/KAFKA-5089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5089. -- Resolution: Fixed Going to close this since it should be resolved by

[jira] [Commented] (KAFKA-4915) Make logging consistent

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16097077#comment-16097077 ] Ewen Cheslack-Postava commented on KAFKA-4915: -- [~dernasherbrezon] No, this is actually

[jira] [Updated] (KAFKA-4915) Don't include "error" in log messages at non-error levels

[ https://issues.apache.org/jira/browse/KAFKA-4915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-4915: - Summary: Don't include "error" in log messages at non-error levels (was: Make

[jira] [Commented] (KAFKA-5635) KIP-181 Kafka-Connect integrate with kafka ReST Proxy

[ https://issues.apache.org/jira/browse/KAFKA-5635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16100399#comment-16100399 ] Ewen Cheslack-Postava commented on KAFKA-5635: -- bq. Kafka connect currently uses kafka

[jira] [Created] (KAFKA-5667) kafka.api.LogDirFailureTest testProduceAfterLogDirFailure flaky test

Ewen Cheslack-Postava created KAFKA-5667: Summary: kafka.api.LogDirFailureTest testProduceAfterLogDirFailure flaky test Key: KAFKA-5667 URL: https://issues.apache.org/jira/browse/KAFKA-5667

[jira] [Commented] (KAFKA-5667) kafka.api.LogDirFailureTest testProduceAfterLogDirFailure flaky test

[ https://issues.apache.org/jira/browse/KAFKA-5667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16103632#comment-16103632 ] Ewen Cheslack-Postava commented on KAFKA-5667: -- [~lindong] I think this was added for the

[jira] [Updated] (KAFKA-5341) Add UnderMinIsrPartitionCount and per-partition UnderMinIsr metrics

[ https://issues.apache.org/jira/browse/KAFKA-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5341: - Fix Version/s: 1.0.0 > Add UnderMinIsrPartitionCount and per-partition

[jira] [Commented] (KAFKA-4327) Move Reset Tool from core to streams

[ https://issues.apache.org/jira/browse/KAFKA-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16101966#comment-16101966 ] Ewen Cheslack-Postava commented on KAFKA-4327: -- [~mjsax] We'd have to decide whether the java

[jira] [Resolved] (KAFKA-5608) System test failure due to timeout starting Jmx tool

[ https://issues.apache.org/jira/browse/KAFKA-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5608. -- Resolution: Fixed Fix Version/s: 0.11.0.1 0.11.1.0

[jira] [Created] (KAFKA-5612) Replace JmxTool with a MetricsReporter in system tests

Ewen Cheslack-Postava created KAFKA-5612: Summary: Replace JmxTool with a MetricsReporter in system tests Key: KAFKA-5612 URL: https://issues.apache.org/jira/browse/KAFKA-5612 Project: Kafka

[jira] [Created] (KAFKA-5613) Deprecate JmxTool?

Ewen Cheslack-Postava created KAFKA-5613: Summary: Deprecate JmxTool? Key: KAFKA-5613 URL: https://issues.apache.org/jira/browse/KAFKA-5613 Project: Kafka Issue Type: Bug Affects

[jira] [Created] (KAFKA-5614) pep8/flake8 checks for system tests

Ewen Cheslack-Postava created KAFKA-5614: Summary: pep8/flake8 checks for system tests Key: KAFKA-5614 URL: https://issues.apache.org/jira/browse/KAFKA-5614 Project: Kafka Issue

[jira] [Commented] (KAFKA-5608) System test failure due to timeout starting Jmx tool

[ https://issues.apache.org/jira/browse/KAFKA-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16094188#comment-16094188 ] Ewen Cheslack-Postava commented on KAFKA-5608: -- For anyone following up, there was quite a

[jira] [Resolved] (KAFKA-5484) Refactor kafkatest docker support

[ https://issues.apache.org/jira/browse/KAFKA-5484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5484. -- Resolution: Fixed Fix Version/s: 0.11.0.1 0.10.2.2

[jira] [Created] (KAFKA-5540) Deprecate and remove internal converter configs

Ewen Cheslack-Postava created KAFKA-5540: Summary: Deprecate and remove internal converter configs Key: KAFKA-5540 URL: https://issues.apache.org/jira/browse/KAFKA-5540 Project: Kafka

[jira] [Commented] (KAFKA-5540) Deprecate and remove internal converter configs

[ https://issues.apache.org/jira/browse/KAFKA-5540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070569#comment-16070569 ] Ewen Cheslack-Postava commented on KAFKA-5540: -- [~umesh9...@gmail.com] Absolutely, please do!

[jira] [Resolved] (KAFKA-5548) SchemaBuilder does not validate input.

[ https://issues.apache.org/jira/browse/KAFKA-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5548. -- Resolution: Fixed Fix Version/s: 0.11.1.0 Issue resolved by pull request

[jira] [Created] (KAFKA-5568) Transformations that mutate topic-partitions break sink connectors that manage their own configuration

Ewen Cheslack-Postava created KAFKA-5568: Summary: Transformations that mutate topic-partitions break sink connectors that manage their own configuration Key: KAFKA-5568 URL:

[jira] [Created] (KAFKA-5704) Auto topic creation causes failure with older clusters

Ewen Cheslack-Postava created KAFKA-5704: Summary: Auto topic creation causes failure with older clusters Key: KAFKA-5704 URL: https://issues.apache.org/jira/browse/KAFKA-5704 Project: Kafka

[jira] [Assigned] (KAFKA-5708) Update Jackson dependencies (from 2.8.5 to 2.9.x)

[ https://issues.apache.org/jira/browse/KAFKA-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5708: Assignee: Dejan Stojadinović (was: Ewen Cheslack-Postava) > Update

[jira] [Commented] (KAFKA-3408) consumer rebalance fail

[ https://issues.apache.org/jira/browse/KAFKA-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16117783#comment-16117783 ] Ewen Cheslack-Postava commented on KAFKA-3408: -- [~airbots] Not sure if it is still an issue

[jira] [Assigned] (KAFKA-5708) Update Jackson dependencies (from 2.8.5 to 2.9.x)

[ https://issues.apache.org/jira/browse/KAFKA-5708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5708: Assignee: Ewen Cheslack-Postava > Update Jackson dependencies (from 2.8.5

[jira] [Resolved] (KAFKA-5704) Auto topic creation causes failure with older clusters

[ https://issues.apache.org/jira/browse/KAFKA-5704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5704. -- Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108328#comment-16108328 ] Ewen Cheslack-Postava commented on KAFKA-2526: -- What is the proposed fix? I don't know that

[jira] [Commented] (KAFKA-2526) Console Producer / Consumer's serde config is not working

[ https://issues.apache.org/jira/browse/KAFKA-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116726#comment-16116726 ] Ewen Cheslack-Postava commented on KAFKA-2526: -- [~ardahal] Yeah, I think the scope of the bug

[jira] [Updated] (KAFKA-5643) Using _DUCKTAPE_OPTIONS has no effect on executing tests

[ https://issues.apache.org/jira/browse/KAFKA-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5643: - Fix Version/s: 0.11.0.1 > Using _DUCKTAPE_OPTIONS has no effect on executing

[jira] [Commented] (KAFKA-5643) Using _DUCKTAPE_OPTIONS has no effect on executing tests

[ https://issues.apache.org/jira/browse/KAFKA-5643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16116046#comment-16116046 ] Ewen Cheslack-Postava commented on KAFKA-5643: -- [~ppatierno] We don't really consider any

[jira] [Resolved] (KAFKA-5742) Support passing ZK chroot in system tests

[ https://issues.apache.org/jira/browse/KAFKA-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5742. -- Resolution: Fixed Fix Version/s: 1.0.0 0.11.0.1 >

[jira] [Resolved] (KAFKA-5567) With transformations that mutate the topic-partition committing offsets should to refer to the original topic-partition

[ https://issues.apache.org/jira/browse/KAFKA-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5567. -- Resolution: Fixed > With transformations that mutate the topic-partition

[jira] [Updated] (KAFKA-5731) Connect WorkerSinkTask out of order offset commit can lead to inconsistent state

[ https://issues.apache.org/jira/browse/KAFKA-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5731: - Fix Version/s: 0.10.2.2 > Connect WorkerSinkTask out of order offset commit can

[jira] [Assigned] (KAFKA-5475) Connector config validation REST API endpoint not including fields for transformations

[ https://issues.apache.org/jira/browse/KAFKA-5475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5475: Assignee: Konstantine Karantasis Reviewer: Ewen Cheslack-Postava >

[jira] [Commented] (KAFKA-4388) Connect key and value converters are listed without default values

[ https://issues.apache.org/jira/browse/KAFKA-4388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16062178#comment-16062178 ] Ewen Cheslack-Postava commented on KAFKA-4388: -- What I meant was that the following: {code}

[jira] [Commented] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16170270#comment-16170270 ] Ewen Cheslack-Postava commented on KAFKA-5716: -- The basic analysis sounds right. That javadoc

[jira] [Assigned] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5716: Assignee: Per Steffensen > Connect: When SourceTask.commit it is possible

[jira] [Commented] (KAFKA-5518) General Kafka connector performanc workload

[ https://issues.apache.org/jira/browse/KAFKA-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16177028#comment-16177028 ] Ewen Cheslack-Postava commented on KAFKA-5518: -- There isn't yet a standard workload. For

[jira] [Assigned] (KAFKA-5896) Kafka Connect task threads never interrupted

[ https://issues.apache.org/jira/browse/KAFKA-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5896: Assignee: Nick Pillitteri > Kafka Connect task threads never interrupted >

[jira] [Commented] (KAFKA-5538) User-specified Producer/Consumer config doesn't effect with KafkaBackingStore(Config/Status/Offset)

[ https://issues.apache.org/jira/browse/KAFKA-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16175839#comment-16175839 ] Ewen Cheslack-Postava commented on KAFKA-5538: -- [~Aegeaner] I like the idea, but let me

[jira] [Commented] (KAFKA-4714) Implement remaining KIP-66 SMTs

[ https://issues.apache.org/jira/browse/KAFKA-4714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16173506#comment-16173506 ] Ewen Cheslack-Postava commented on KAFKA-4714: -- [~dhananjaydp] You cannot do that with SMTs,

[jira] [Resolved] (KAFKA-5657) Connect REST API should include the connector type when describing a connector

[ https://issues.apache.org/jira/browse/KAFKA-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5657. -- Resolution: Fixed Issue resolved by pull request 3812

[jira] [Resolved] (KAFKA-5330) Use per-task converters in Connect

[ https://issues.apache.org/jira/browse/KAFKA-5330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5330. -- Resolution: Fixed Fix Version/s: 1.0.0 Issue resolved by pull request

[jira] [Assigned] (KAFKA-5657) Connect REST API should include the connector type when describing a connector

[ https://issues.apache.org/jira/browse/KAFKA-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-5657: Assignee: Ted Yu > Connect REST API should include the connector type when

[jira] [Updated] (KAFKA-5657) Connect REST API should include the connector type when describing a connector

[ https://issues.apache.org/jira/browse/KAFKA-5657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-5657: - Labels: needs-kip (was: needs-kip newbie) > Connect REST API should include the

[jira] [Resolved] (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 ] Ewen Cheslack-Postava resolved KAFKA-5953. -- Resolution: Fixed Fix Version/s: 1.0.0 1.1.0 Issue

[jira] [Resolved] (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 ] Ewen Cheslack-Postava resolved KAFKA-5902. -- Resolution: Fixed Issue resolved by pull request 3975

[jira] [Created] (KAFKA-6009) Fix formatting of autogenerated docs tables

Ewen Cheslack-Postava created KAFKA-6009: Summary: Fix formatting of autogenerated docs tables Key: KAFKA-6009 URL: https://issues.apache.org/jira/browse/KAFKA-6009 Project: Kafka

[jira] [Commented] (KAFKA-4029) SSL support for Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197603#comment-16197603 ] Ewen Cheslack-Postava commented on KAFKA-4029: -- Oh, and I should say that wherever the

[jira] [Commented] (KAFKA-4029) SSL support for Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-4029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197602#comment-16197602 ] Ewen Cheslack-Postava commented on KAFKA-4029: -- I think the KIP's goal of keeping the

[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 ] Ewen Cheslack-Postava updated KAFKA-6007: - Component/s: KafkaConnect > Connect can't validate against transforms in

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

[ https://issues.apache.org/jira/browse/KAFKA-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5903. -- Resolution: Fixed Issue resolved by pull request 4011

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

[ https://issues.apache.org/jira/browse/KAFKA-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155820#comment-16155820 ] Ewen Cheslack-Postava commented on KAFKA-5774: -- I think this is already fixed in trunk:

[jira] [Commented] (KAFKA-5741) Prioritize threads in Connect distributed worker process

[ https://issues.apache.org/jira/browse/KAFKA-5741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16155857#comment-16155857 ] Ewen Cheslack-Postava commented on KAFKA-5741: -- It would be good to have clear indications

[jira] [Commented] (KAFKA-5716) Connect: When SourceTask.commit it is possible not everthing from SourceTask.poll has been sent

[ https://issues.apache.org/jira/browse/KAFKA-5716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178406#comment-16178406 ] Ewen Cheslack-Postava commented on KAFKA-5716: -- Sorry, I was just doing a round of cleanup on

[jira] [Resolved] (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 ] Ewen Cheslack-Postava resolved KAFKA-5900. -- Resolution: Fixed Reviewer: Ewen Cheslack-Postava Fixed via

[jira] [Created] (KAFKA-6011) AppInfoParser should only use metrics API and should not register JMX mbeans directly

Ewen Cheslack-Postava created KAFKA-6011: Summary: AppInfoParser should only use metrics API and should not register JMX mbeans directly Key: KAFKA-6011 URL:

[jira] [Resolved] (KAFKA-6008) Kafka Connect: Unsanitized workerID causes exception during startup

[ https://issues.apache.org/jira/browse/KAFKA-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6008. -- Resolution: Fixed Issue resolved by pull request 4012

[jira] [Commented] (KAFKA-6011) AppInfoParser should only use metrics API and should not register JMX mbeans directly

[ https://issues.apache.org/jira/browse/KAFKA-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16192105#comment-16192105 ] Ewen Cheslack-Postava commented on KAFKA-6011: -- [~rsivaram] Fair point, I see that we have

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

[ https://issues.apache.org/jira/browse/KAFKA-5990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5990. -- Resolution: Fixed Issue resolved by pull request 3987

[jira] [Commented] (KAFKA-6008) Kafka Connect: Unsanitized workerID causes exception during startup

[ https://issues.apache.org/jira/browse/KAFKA-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16191770#comment-16191770 ] Ewen Cheslack-Postava commented on KAFKA-6008: -- Good catch, I actually don't think that

[jira] [Assigned] (KAFKA-6008) Kafka Connect: Unsanitized workerID causes exception during startup

[ https://issues.apache.org/jira/browse/KAFKA-6008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-6008: Assignee: Jakub Scholz > Kafka Connect: Unsanitized workerID causes

[jira] [Resolved] (KAFKA-6087) Scanning plugin.path needs to support relative symlinks

[ https://issues.apache.org/jira/browse/KAFKA-6087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6087. -- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request

[jira] [Resolved] (KAFKA-5563) Clarify handling of connector name in config

[ https://issues.apache.org/jira/browse/KAFKA-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5563. -- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request

[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=16265886#comment-16265886 ] Ewen Cheslack-Postava commented on KAFKA-6168: -- [~tedyu] I think the best next step before

[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 ] Ewen Cheslack-Postava resolved KAFKA-4827. -- Resolution: Fixed Fix Version/s: (was: 0.11.0.3)

[jira] [Resolved] (KAFKA-6284) System Test failed: ConnectRestApiTest

[ https://issues.apache.org/jira/browse/KAFKA-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6284. -- Resolution: Fixed Issue resolved by pull request 4279

[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 ] Ewen Cheslack-Postava updated KAFKA-4827: - Fix Version/s: 0.11.0.3 0.10.2.2 0.10.1.2

[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 ] Ewen Cheslack-Postava updated KAFKA-6311: - Fix Version/s: 1.1.0 > Expose Kafka cluster ID in Connect REST API >

[jira] [Commented] (KAFKA-6048) Support negative record timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257265#comment-16257265 ] Ewen Cheslack-Postava commented on KAFKA-6048: -- A less intrusive change would be to just

[jira] [Commented] (KAFKA-6223) Please delete old releases from mirroring system

[ https://issues.apache.org/jira/browse/KAFKA-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258719#comment-16258719 ] Ewen Cheslack-Postava commented on KAFKA-6223: -- Should we maybe consider two use cases for

[jira] [Commented] (KAFKA-5842) QueryableStateIntegrationTest may fail with JDK 7

[ https://issues.apache.org/jira/browse/KAFKA-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16261623#comment-16261623 ] Ewen Cheslack-Postava commented on KAFKA-5842: -- I've also now seen this in a JDK8 job too on

[jira] [Resolved] (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 ] Ewen Cheslack-Postava resolved KAFKA-6168. -- Resolution: Fixed Fix Version/s: 1.1.0 Issue resolved by pull request

[jira] [Created] (KAFKA-6253) Improve sink connector topic regex validation

Ewen Cheslack-Postava created KAFKA-6253: Summary: Improve sink connector topic regex validation Key: KAFKA-6253 URL: https://issues.apache.org/jira/browse/KAFKA-6253 Project: Kafka

[jira] [Assigned] (KAFKA-6218) Optimize condition in if statement to reduce the number of comparisons

[ https://issues.apache.org/jira/browse/KAFKA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-6218: Assignee: sachin bhalekar > Optimize condition in if statement to reduce

[jira] [Resolved] (KAFKA-6218) Optimize condition in if statement to reduce the number of comparisons

[ https://issues.apache.org/jira/browse/KAFKA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6218. -- Resolution: Fixed Reviewer: Ewen Cheslack-Postava > Optimize condition in

[jira] [Updated] (KAFKA-6218) Optimize condition in if statement to reduce the number of comparisons

[ https://issues.apache.org/jira/browse/KAFKA-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6218: - Fix Version/s: 1.1.0 > Optimize condition in if statement to reduce the number of

[jira] [Updated] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6148: - Summary: ClassCastException in BigQuery connector (was: ERROR Commit of

[jira] [Commented] (KAFKA-6161) Introduce new serdes interfaces with empty configure() and close()

[ https://issues.apache.org/jira/browse/KAFKA-6161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16239114#comment-16239114 ] Ewen Cheslack-Postava commented on KAFKA-6161: -- It would need a KIP as new public API, but

[jira] [Assigned] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava reassigned KAFKA-6148: Assignee: Konstantine Karantasis > ClassCastException in BigQuery

[jira] [Commented] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238589#comment-16238589 ] Ewen Cheslack-Postava commented on KAFKA-6148: -- I think this is due to the new classpath

[jira] [Commented] (KAFKA-6148) ClassCastException in BigQuery connector

[ https://issues.apache.org/jira/browse/KAFKA-6148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16238621#comment-16238621 ] Ewen Cheslack-Postava commented on KAFKA-6148: -- [~burd0047] Can you clarify which version of

[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=16286767#comment-16286767 ] Ewen Cheslack-Postava commented on KAFKA-6311: -- PR available here:

[jira] [Commented] (KAFKA-4083) ReassignPartitionsCommand does not check replication factor

[ https://issues.apache.org/jira/browse/KAFKA-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226194#comment-16226194 ] Ewen Cheslack-Postava commented on KAFKA-4083: -- Presumably it is

[jira] [Commented] (KAFKA-6891) send.buffer.bytes should be allowed to set -1 in KafkaConnect

[ https://issues.apache.org/jira/browse/KAFKA-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16469767#comment-16469767 ] Ewen Cheslack-Postava commented on KAFKA-6891: -- [~olkuznsmith] Yeah, agreed. The validation

[jira] [Commented] (KAFKA-6914) Kafka Connect - Plugins class should have a constructor that can take in parent ClassLoader

[ https://issues.apache.org/jira/browse/KAFKA-6914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16486603#comment-16486603 ] Ewen Cheslack-Postava commented on KAFKA-6914: -- [~sriramks85] Not sure I understand the use

[jira] [Resolved] (KAFKA-5807) Check Connector.config() and Transformation.config() returns a valid ConfigDef

[ https://issues.apache.org/jira/browse/KAFKA-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-5807. -- Resolution: Fixed Fix Version/s: 2.0.0 Issue resolved by pull request

[jira] [Updated] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6566: - Fix Version/s: 1.1.1 1.0.2 0.11.0.3 >

[jira] [Resolved] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-6566. -- Resolution: Fixed > SourceTask#stop() not called after exception raised in

[jira] [Updated] (KAFKA-6566) SourceTask#stop() not called after exception raised in poll()

[ https://issues.apache.org/jira/browse/KAFKA-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava updated KAFKA-6566: - Reviewer: Ewen Cheslack-Postava > SourceTask#stop() not called after exception

  1   2   3   >