Re: Something like a unique key to prevent same record from being inserted twice?

On 2019/04/02 22:43:31, jim.me...@concept-solutions.com wrote: > > > On 2019/04/02 22:25:16, jim.me...@concept-solutions.com > wrote: > > > > > > On 2019/04/02 21:59:21, Hans Jespersen wrote: > > > yes. Idempotent publish uses a unique messageID to discard potential > > > duplicate

Re: Race condition with stream use of Global KTable

Yes, I forgot to show an item on the topology: +---> global-ktable +-+ | | + v topic-1stream +> topic-3 + ^ |

Re: Race condition with stream use of Global KTable

Hello Raman, It seems from your case that `topic-1` is used for both the global ktable as well as another stream, which then be transformed to a new stream that will be "joined" somehow with the global ktable. Could you elaborate your case a bit more on why do you want to use the same source topic

Re: Something like a unique key to prevent same record from being inserted twice?

On 2019/04/02 22:25:16, jim.me...@concept-solutions.com wrote: > > > On 2019/04/02 21:59:21, Hans Jespersen wrote: > > yes. Idempotent publish uses a unique messageID to discard potential > > duplicate messages caused by failure conditions when publishing. > > > > -hans > > > > > On

Race condition with stream use of Global KTable

I have a topology like this: +---> global-ktable +-+ | | + v topic-1stream + ^ | | +

Re: Something like a unique key to prevent same record from being inserted twice?

On 2019/04/02 21:59:21, Hans Jespersen wrote: > yes. Idempotent publish uses a unique messageID to discard potential > duplicate messages caused by failure conditions when publishing. > > -hans > > > On Apr 1, 2019, at 9:49 PM, jim.me...@concept-solutions.com > > wrote: > > > > Does K

Re: Something like a unique key to prevent same record from being inserted twice?

yes. Idempotent publish uses a unique messageID to discard potential duplicate messages caused by failure conditions when publishing. -hans > On Apr 1, 2019, at 9:49 PM, jim.me...@concept-solutions.com > wrote: > > Does Kafka have something that behaves like a unique key so a producer can’

Something like a unique key to prevent same record from being inserted twice?

Does Kafka have something that behaves like a unique key so a producer can’t write the same value to a topic twice?

Re: Strange KafkaConsumer IllegalStateException

Further investigation has uncovered a defect when resolving a hostname fails - https://issues.apache.org/jira/browse/KAFKA-8182 Looks like it has been present since support for resolving all DNS IPs was added. On Mon, 1 Apr 2019 at 15:55, Mark Anderson wrote: > Hi list, > > I've a question rega

Re: leader none, with only one replicat end no ISR

Hello Adrien Could you give more details about your topic configurations (how many partitions, what is the replication factor ?) Usually, partition operations are performed by a broker that has been assigned as the "controller". You should be able to check the controller broker id with this comma