Jenkins build is back to normal : kafka-trunk-jdk11 #377

2019-03-15 Thread Apache Jenkins Server
See

Build failed in Jenkins: kafka-trunk-jdk8 #3470

2019-03-15 Thread Apache Jenkins Server
See Changes: [github] MINOR: Update code to not use deprecated methods (#6434) [mjsax] KAFKA-7855: Kafka Streams Maven Archetype quickstart fails to compile -- [...trunca

[jira] [Created] (KAFKA-8116) Add Kafka Streams archetype for Java11

2019-03-15 Thread Matthias J. Sax (JIRA)
Matthias J. Sax created KAFKA-8116: -- Summary: Add Kafka Streams archetype for Java11 Key: KAFKA-8116 URL: https://issues.apache.org/jira/browse/KAFKA-8116 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-8115) Flaky Test CoordinatorTest#testTaskRequestWithOldStartMsGetsUpdated

2019-03-15 Thread Matthias J. Sax (JIRA)
Matthias J. Sax created KAFKA-8115: -- Summary: Flaky Test CoordinatorTest#testTaskRequestWithOldStartMsGetsUpdated Key: KAFKA-8115 URL: https://issues.apache.org/jira/browse/KAFKA-8115 Project: Kafka

[jira] [Created] (KAFKA-8114) Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoGroupAcl

2019-03-15 Thread Matthias J. Sax (JIRA)
Matthias J. Sax created KAFKA-8114: -- Summary: Flaky Test DelegationTokenEndToEndAuthorizationTest#testNoGroupAcl Key: KAFKA-8114 URL: https://issues.apache.org/jira/browse/KAFKA-8114 Project: Kafka

[jira] [Created] (KAFKA-8113) Flaky Test ListOffsetsRequestTest#testResponseIncludesLeaderEpoch

2019-03-15 Thread Matthias J. Sax (JIRA)
Matthias J. Sax created KAFKA-8113: -- Summary: Flaky Test ListOffsetsRequestTest#testResponseIncludesLeaderEpoch Key: KAFKA-8113 URL: https://issues.apache.org/jira/browse/KAFKA-8113 Project: Kafka

[jira] [Created] (KAFKA-8112) Add system test to detect compatibility issues when requests are updated

2019-03-15 Thread Rajini Sivaram (JIRA)
Rajini Sivaram created KAFKA-8112: - Summary: Add system test to detect compatibility issues when requests are updated Key: KAFKA-8112 URL: https://issues.apache.org/jira/browse/KAFKA-8112 Project: Kaf

Build failed in Jenkins: kafka-trunk-jdk8 #3469

2019-03-15 Thread Apache Jenkins Server
See Changes: [github] KAFKA-8091; Use commitSync to check connection failure in listener [colin] MINOR: Update Trogdor ConnectionStressWorker status at the end of -- [...

Build failed in Jenkins: kafka-trunk-jdk11 #376

2019-03-15 Thread Apache Jenkins Server
See Changes: [github] KAFKA-8091; Use commitSync to check connection failure in listener [colin] MINOR: Update Trogdor ConnectionStressWorker status at the end of -- [...

Re: [VOTE] KIP-415: Incremental Cooperative Rebalancing in Kafka Connect

2019-03-15 Thread Konstantine Karantasis
Thank you all for the votes and your comments! KIP-415 has been accepted with +4 binding votes (Guozhang, Jason, Randall, Ewen) and +4 non-binding votes (Ryanne, Rhys, Robert, Satish). Best, Konstantine On Thu, Mar 14, 2019 at 10:24 PM Satish Duggana wrote: > Nice work Konstantine! > +1 (non-

Jenkins build is back to normal : kafka-2.2-jdk8 #59

2019-03-15 Thread Apache Jenkins Server
See

Build failed in Jenkins: kafka-trunk-jdk8 #3468

2019-03-15 Thread Apache Jenkins Server
See Changes: [bbejeck] KAFKA-7027: Add an overload build method in scala (#6373) -- [...truncated 4.68 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFa

Re: Guava version upgrade

2019-03-15 Thread Colin McCabe
Hi JIAHAO, Kafka does not use Guava. Some of the packages Kafka Connect depend on use Guava. Perhaps the right thing to do is track down those projects and see how they are using Guava (if they are vulnerable to the CVE). best, Colin On Mon, Mar 4, 2019, at 15:52, JIAHAO ZHOU wrote: > Hello

[jira] [Created] (KAFKA-8111) KafkaProducer can't produce data

2019-03-15 Thread John Roesler (JIRA)
John Roesler created KAFKA-8111: --- Summary: KafkaProducer can't produce data Key: KAFKA-8111 URL: https://issues.apache.org/jira/browse/KAFKA-8111 Project: Kafka Issue Type: Bug Compon

Re: [DISCUSSION] KIP-407

2019-03-15 Thread Ryanne Dolan
Maybe mark it abandoned? fwiw, I think both KIPs break the worker-vs-connector boundary that, for better or worse, is fundamental to Connect's architecture and APIs. An alternative came up a few times during discussions for KIP-382: support multiple "herders" within the same Connect cluster. Each

[jira] [Created] (KAFKA-8110) Flaky Test DescribeConsumerGroupTest#testDescribeMembersWithConsumersWithoutAssignedPartitions

2019-03-15 Thread Matthias J. Sax (JIRA)
Matthias J. Sax created KAFKA-8110: -- Summary: Flaky Test DescribeConsumerGroupTest#testDescribeMembersWithConsumersWithoutAssignedPartitions Key: KAFKA-8110 URL: https://issues.apache.org/jira/browse/KAFKA-8110

Re: Kafka Streams Join does not work

2019-03-15 Thread Ryanne Dolan
If your producer is using transactions, it's possible that the producer was killed in the middle of a transaction, in which case any un-committed records would be logged on the broker but skipped by downstream consumers. Otherwise, it's likely that the leader for the partition crashed before the r

Re: [DISCUSS] KIP-437: Custom replacement for MaskField SMT

2019-03-15 Thread Valeria Vasylieva
Hi Adam, Thank you for your interest. Here is the list of currently supported transformations in Connect: https://kafka.apache.org/documentation/#connect_transforms. As I can see, there is no "map" transformation in this list and all other SMTs do not support functionality described in a KIP. I ca

Re: Kafka Streams Join does not work

2019-03-15 Thread Федор Чернилин
Thanks, I understand how consumer works. The main question is related to why the join did not work and how it happened that only one message remained uncommitted. пт, 15 мар. 2019 г. в 16:29, Ryanne Dolan : > Hello! When using exactly-once semantics, uncommitted or aborted records > are skipped b

Re: [DISCUSS] KIP-437: Custom replacement for MaskField SMT

2019-03-15 Thread Adam Bellemare
Hi Valeria Thanks for the KIP. I admit my knowledge on Kafka Connect transforms is a bit rusty, however - Is there any other way to currently achieve this same functionality outlined in your KIP using existing transforms? Thanks On Thu, Mar 14, 2019 at 12:05 PM Valeria Vasylieva < valeri

[DISCUSSION] KIP-407

2019-03-15 Thread Randall Hauch
https://cwiki.apache.org/confluence/display/KAFKA/KIP-407%3A+Kafka+Connect+support+override+worker+kafka+api+configuration+with+connector+configuration+that+post+by+rest+api was created by the author and a discussion thread was never started. This appears to very similar to (or rather a subset of)

Re: Kafka Streams Join does not work

2019-03-15 Thread Ryanne Dolan
Hello! When using exactly-once semantics, uncommitted or aborted records are skipped by the consumer as if they don't exist. When inspecting the topic manually, use isolation.level=read_committed to get the same behavior. Ryanne On Fri, Mar 15, 2019, 6:08 AM Федор Чернилин wrote: > I also noti

Jenkins build is back to normal : kafka-trunk-jdk8 #3467

2019-03-15 Thread Apache Jenkins Server
See

Re: Kafka Streams Join does not work

2019-03-15 Thread Федор Чернилин
I also noticed another important thing now. Message which used for join is uncommitted. I understood it with the help of consumer's setting isolation level - read_committed. The message got into the topic using the same stream app. Remind that stream app has processing guarantee = exactly_once. How

[jira] [Created] (KAFKA-8109) Consumer with isolation level as 'read_committed' are getting stuck for few partitions

2019-03-15 Thread Love Singh (JIRA)
Love Singh created KAFKA-8109: - Summary: Consumer with isolation level as 'read_committed' are getting stuck for few partitions Key: KAFKA-8109 URL: https://issues.apache.org/jira/browse/KAFKA-8109 Projec

Kafka Streams Join does not work

2019-03-15 Thread Федор Чернилин
Hello! I encountered the following problem. I have 3 brokers and 1 zookeper. Topics with 10 partitions and replication factor 3. Stream app with 10 threads, exactly_once and commit interval 1000ms. When I run stream app, join of 2 my topics doesn't work for specific message. But for all another mes

Jenkins build is back to normal : kafka-trunk-jdk11 #374

2019-03-15 Thread Apache Jenkins Server
See

Build failed in Jenkins: kafka-trunk-jdk8 #3466

2019-03-15 Thread Apache Jenkins Server
See Changes: [wangguoz] KAFKA-7502: Cleanup KTable materialization logic in a single place -- [...truncated 2.35 MB...] org.apache.kafka.streams.test.OutputVerifierTest >