Re: Workaround for KTable/KTable join followed by groupBy and aggregate/count can result in duplicated results KAFKA-4609?

Hi John, thanks. Yes, using hashes is what I already do. Thank you for excellent explanation. Best Regards Artur On Tue, May 1, 2018 at 9:29 PM, John Roesler wrote: > Hi Artur, > > Thanks for the clarification. > > I don't think that ".toStream()" actually does anything besides change the > con

Re: Workaround for KTable/KTable join followed by groupBy and aggregate/count can result in duplicated results KAFKA-4609?

Hi Artur, Thanks for the clarification. I don't think that ".toStream()" actually does anything besides change the context from KTable to KStream in the DSL. The Javadoc says: * Note that this is a logical operation and only changes the > "interpretation" of the stream, i.e., each record of > *

Re: Workaround for KTable/KTable join followed by groupBy and aggregate/count can result in duplicated results KAFKA-4609?

Hi John, yes, the answer is very helpful and your understanding of the data flow is correct. Although, deduplication is not the issue because there will not be any duplicates inserted into the flow. These, the duplicates will be generated, from unique records after the join between claim and paymen

Re: Kafka-Connect : Invalid value java.sql.SQLException: No suitable driver found for jdbc:mysql://127.0.0.1:3306/connect_test

Hi, Below are the mysql jar files directories. $ docker exec -it kafka-connect-avro bashroot@default:/# ls -lrt /etc/kafka-connect-jdbc/total 976-rw-r--r-- 1 root root   1386 Apr 16 17:42 source-quickstart-sqlite.properties-rw-r--r-- 1 root root   1169 Apr 16 17:42 sink-quickstart-sqlite.propert

Re: Kafka-Connect : Invalid value java.sql.SQLException: No suitable driver found for jdbc:mysql://127.0.0.1:3306/connect_test

Thank you Ted, Gone through the link and removed the custom CONNECT_PLUGIN_PATH. Now getting below error. Executed below commands in same sequence for creating connector and jdbc. 1)docker run -d \  --name=kafka-connect-avro \  --net=host \  -e CONNECT_BOOTSTRAP_SERVERS=localhost:29092 \  -e CON

Re: Kafka-Connect : Invalid value java.sql.SQLException: No suitable driver found for jdbc:mysql://127.0.0.1:3306/connect_test

Have you seen this thread ? https://stackoverflow.com/questions/49433199/kafka-connect-jdbc-source-connector-not-working-for-microsoft-sql-server On Tue, May 1, 2018 at 5:52 AM, Jagannath Bilgi wrote: > Hi Team, > Getting subject error message while trying to create Kafka-JDBC > connector. Abl

Kafka-Connect : Invalid value java.sql.SQLException: No suitable driver found for jdbc:mysql://127.0.0.1:3306/connect_test

Hi Team, Getting subject error message while trying to  create Kafka-JDBC connector.  Able to execute initial steps successfully from Kafka Connect Tutorial — Confluent Platform However it fails on executing below command. curl -X POST   -H "Content-Type: application/json"   --data '{ "name": "qu

ApacheCon North America 2018 schedule is now live.

Dear Apache Enthusiast, We are pleased to announce our schedule for ApacheCon North America 2018. ApacheCon will be held September 23-27 at the Montreal Marriott Chateau Champlain in Montreal, Canada. Registration is open! The early bird rate of $575 lasts until July 21, at which time it goe