[jira] [Resolved] (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:all-tabpanel ] Randall Hauch resolved KAFKA-5505. -- Resolution: Fixed Reviewer: Randall Hauch > Connect: Do not restart connector and

[jira] [Updated] (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:all-tabpanel ] Randall Hauch updated KAFKA-5505: - Fix Version/s: 2.3.0 Merged onto `trunk` for AK 2.3.0. > Connect: Do not restart connector and

[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=16841884#comment-16841884 ] ASF GitHub Bot commented on KAFKA-5505: --- rhauch commented on pull request #6363: KAFKA-5505:

[jira] [Comment Edited] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841851#comment-16841851 ] Kun Song edited comment on KAFKA-7895 at 5/17/19 2:03 AM: -- Hi [~vvcephei],

[jira] [Commented] (KAFKA-7895) Ktable supress operator emitting more than one record for the same key per window

[ https://issues.apache.org/jira/browse/KAFKA-7895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841851#comment-16841851 ] Kun Song commented on KAFKA-7895: - Hi [~vvcephei], Great work! I want to test it in my env, but I can't

[jira] [Commented] (KAFKA-6455) Improve timestamp propagation at DSL level

[ https://issues.apache.org/jira/browse/KAFKA-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841847#comment-16841847 ] ASF GitHub Bot commented on KAFKA-6455: --- mjsax commented on pull request #6751: KAFKA-6455: Update

[jira] [Resolved] (KAFKA-3522) Consider adding version information into rocksDB storage format

[ https://issues.apache.org/jira/browse/KAFKA-3522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3522. Resolution: Fixed Fix Version/s: 2.3.0 > Consider adding version information into

[jira] [Commented] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841748#comment-16841748 ] Sophie Blee-Goldman commented on KAFKA-8367: Hm. I notice in going from 2.0 to 2.1 we

[jira] [Comment Edited] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841748#comment-16841748 ] Sophie Blee-Goldman edited comment on KAFKA-8367 at 5/16/19 9:46 PM: -

[jira] [Commented] (KAFKA-8309) KIP-465: Add Consolidated Connector Endpoint to Connect REST API

[ https://issues.apache.org/jira/browse/KAFKA-8309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841739#comment-16841739 ] ASF GitHub Bot commented on KAFKA-8309: --- rhauch commented on pull request #6658: KAFKA-8309: Add

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841710#comment-16841710 ] Matthias J. Sax commented on KAFKA-8315: Don't think that should be required? The way Kafka

[jira] [Commented] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841701#comment-16841701 ] ASF GitHub Bot commented on KAFKA-8376: --- ijuma commented on pull request #6746: KAFKA-8376; Least

[jira] [Created] (KAFKA-8377) KTable#transformValue might lead to incorrect result in joins

Matthias J. Sax created KAFKA-8377: -- Summary: KTable#transformValue might lead to incorrect result in joins Key: KAFKA-8377 URL: https://issues.apache.org/jira/browse/KAFKA-8377 Project: Kafka

[jira] [Resolved] (KAFKA-8256) Replace Heartbeat request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8256. Resolution: Fixed > Replace Heartbeat request/response with automated protocol >

[jira] [Commented] (KAFKA-8256) Replace Heartbeat request/response with automated protocol

[ https://issues.apache.org/jira/browse/KAFKA-8256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841686#comment-16841686 ] ASF GitHub Bot commented on KAFKA-8256: --- hachikuji commented on pull request #6691: KAFKA-8256:

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841640#comment-16841640 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:55 PM: Also, I had a thought

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841640#comment-16841640 ] Andrew commented on KAFKA-8315: --- Also, I had a thought whether you could modify

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841635#comment-16841635 ] Matthias J. Sax commented on KAFKA-8315: {quote}as the limit is on the fetch, and the queue cant

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:40 PM: Well, Im not sure that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:32 PM: Well, Im not sure that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:30 PM: Well, Im not sure that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:29 PM: Well, Im not sure that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:28 PM: Well, Im not sure that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew edited comment on KAFKA-8315 at 5/16/19 6:16 PM: Well, Im not sure that

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841611#comment-16841611 ] Andrew commented on KAFKA-8315: --- Well, Im not sure that just fixing the start is sufficient. I suspect that

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841571#comment-16841571 ] John Roesler edited comment on KAFKA-8315 at 5/16/19 5:50 PM: -- Oh, man. I'm

[jira] [Resolved] (KAFKA-6852) Allow Log Levels to be dynamically configured

[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yeva Byzek resolved KAFKA-6852. --- Resolution: Duplicate This is getting addressed in KAFKA-7800 > Allow Log Levels to be dynamically

[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured

[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841574#comment-16841574 ] Addison commented on KAFKA-6852: Very true.  Because KAFKA-7800 is linked to the KIP can we close this

[jira] [Comment Edited] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841571#comment-16841571 ] John Roesler edited comment on KAFKA-8315 at 5/16/19 5:42 PM: -- Oh, man. I'm

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841571#comment-16841571 ] John Roesler commented on KAFKA-8315: - Oh, man. I'm sorry that that I didn't convey the significance

[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured

[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841560#comment-16841560 ] Yeva Byzek commented on KAFKA-6852: --- [~ahuddy] Technically speaking, KAFKA-7800 is a dupe of this one,

[jira] [Commented] (KAFKA-8163) SetSchemaMetadata SMT does not apply to nested types

[ https://issues.apache.org/jira/browse/KAFKA-8163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841564#comment-16841564 ] Marc Löhe commented on KAFKA-8163: -- I experience the same problem with Connect 2.2 and Debezium 0.9.5.

[jira] [Commented] (KAFKA-6852) Allow Log Levels to be dynamically configured

[ https://issues.apache.org/jira/browse/KAFKA-6852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841555#comment-16841555 ] Addison commented on KAFKA-6852: [~yevabyzek] I think this is a duplicate of 

[jira] [Commented] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841496#comment-16841496 ] ASF GitHub Bot commented on KAFKA-8376: --- hachikuji commented on pull request #6746: KAFKA-8376;

[jira] [Commented] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841478#comment-16841478 ] Jason Gustafson commented on KAFKA-8376: This could be caused by KAFKA-8275. I will have a patch

[jira] [Assigned] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

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

[jira] [Commented] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841464#comment-16841464 ] Raman Gupta commented on KAFKA-6817: Same problem here, with a stream that is intended to migrate

[jira] [Comment Edited] (KAFKA-6817) UnknownProducerIdException when writing messages with old timestamps

[ https://issues.apache.org/jira/browse/KAFKA-6817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841464#comment-16841464 ] Raman Gupta edited comment on KAFKA-6817 at 5/16/19 3:30 PM: - Same problem

[jira] [Commented] (KAFKA-8367) Non-heap memory leak in Kafka Streams

[ https://issues.apache.org/jira/browse/KAFKA-8367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841452#comment-16841452 ] Pavel Savov commented on KAFKA-8367: Hi [~vvcephei] and [~ableegoldman], Thank you for your

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841449#comment-16841449 ] Andrew commented on KAFKA-8315: --- [~mjsax] [~vvcephei] [~ableegoldman] Thanks for your help on this, I think

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841378#comment-16841378 ] Matthias J. Sax commented on KAFKA-8315: 1) I think, 6719 should make it into 2.3 release. 2)

[jira] [Commented] (KAFKA-8347) Choose next record to process by timestamp

[ https://issues.apache.org/jira/browse/KAFKA-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841383#comment-16841383 ] ASF GitHub Bot commented on KAFKA-8347: --- bbejeck commented on pull request #6719: KAFKA-8347:

[jira] [Updated] (KAFKA-8347) Choose next record to process by timestamp

[ https://issues.apache.org/jira/browse/KAFKA-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-8347: --- Affects Version/s: 2.3.0 > Choose next record to process by timestamp >

[jira] [Updated] (KAFKA-8347) Choose next record to process by timestamp

[ https://issues.apache.org/jira/browse/KAFKA-8347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck updated KAFKA-8347: --- Fix Version/s: 2.3.0 > Choose next record to process by timestamp >

[jira] [Commented] (KAFKA-8220) Avoid kicking out members through rebalance timeout

[ https://issues.apache.org/jira/browse/KAFKA-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841319#comment-16841319 ] ASF GitHub Bot commented on KAFKA-8220: --- hachikuji commented on pull request #: KAFKA-8220 &

[jira] [Resolved] (KAFKA-8220) Avoid kicking out members through rebalance timeout

[ https://issues.apache.org/jira/browse/KAFKA-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-8220. Resolution: Fixed > Avoid kicking out members through rebalance timeout >

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841273#comment-16841273 ] Andrew commented on KAFKA-8315: --- Ha!, you are absolutely right. Maybe I didn't understand the significance

[jira] [Commented] (KAFKA-8078) Flaky Test TableTableJoinIntegrationTest#testInnerInner

[ https://issues.apache.org/jira/browse/KAFKA-8078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841269#comment-16841269 ] Matthias J. Sax commented on KAFKA-8078: Different error message: 

[jira] [Commented] (KAFKA-3816) Provide more context in Kafka Connect log messages using MDC

[ https://issues.apache.org/jira/browse/KAFKA-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841234#comment-16841234 ] ASF GitHub Bot commented on KAFKA-3816: --- guozhangwang commented on pull request #5743: KAFKA-3816:

[jira] [Commented] (KAFKA-7941) Connect KafkaBasedLog work thread terminates when getting offsets fails because broker is unavailable

[ https://issues.apache.org/jira/browse/KAFKA-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841226#comment-16841226 ] Randall Hauch commented on KAFKA-7941: -- It looks like KAFKA-6608 changed the

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841219#comment-16841219 ] Matthias J. Sax commented on KAFKA-8315: John mentioned the max task idle config earlier in this

[jira] [Commented] (KAFKA-8315) Historical join issues

[ https://issues.apache.org/jira/browse/KAFKA-8315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841213#comment-16841213 ] Andrew commented on KAFKA-8315: --- [~vvcephei] [~ableegoldman] Using the integration test I think I now

[jira] [Comment Edited] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841208#comment-16841208 ] Manikumar edited comment on KAFKA-8376 at 5/16/19 10:44 AM: [~viktorsomogyi]

[jira] [Commented] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

[ https://issues.apache.org/jira/browse/KAFKA-8376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16841208#comment-16841208 ] Manikumar commented on KAFKA-8376: -- [~viktorsomogyi] Can you check, if this is related to

[jira] [Created] (KAFKA-8376) Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test.

Manikumar created KAFKA-8376: Summary: Flaky test ClientAuthenticationFailureTest.testTransactionalProducerWithInvalidCredentials test. Key: KAFKA-8376 URL: https://issues.apache.org/jira/browse/KAFKA-8376

[jira] [Updated] (KAFKA-8375) Offset jumps back after commit

[ https://issues.apache.org/jira/browse/KAFKA-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Dybeck updated KAFKA-8375: - Description: *Setup* Kafka: 1.1.1 Kafka-client: 1.1.1 Zookeeper: 3.4.11 Akka streams: 0.20

[jira] [Updated] (KAFKA-8375) Offset jumps back after commit

[ https://issues.apache.org/jira/browse/KAFKA-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Dybeck updated KAFKA-8375: - Attachment: (was: Skärmavbild 2019-05-16 kl. 08.41.53.png) > Offset jumps back after commit

[jira] [Updated] (KAFKA-8375) Offset jumps back after commit

[ https://issues.apache.org/jira/browse/KAFKA-8375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Markus Dybeck updated KAFKA-8375: - Attachment: partition_lag_metrics.png > Offset jumps back after commit >

[jira] [Created] (KAFKA-8375) Offset jumps back after commit

Markus Dybeck created KAFKA-8375: Summary: Offset jumps back after commit Key: KAFKA-8375 URL: https://issues.apache.org/jira/browse/KAFKA-8375 Project: Kafka Issue Type: Bug