Issue using Https with elasticsearch source connector

Hello team, Can anyone help me with this issue? https://github.com/DarioBalinzo/kafka-connect-elasticsearch-source/issues/44 Regards, Sunil.

Re: Modify kafka-connect api context path

--server.servlet.context-path="/kafdrop" Something like this ? https://github.com/obsidiandynamics/kafdrop/issues/9 בתאריך יום ד׳, 26 במאי 2021, 23:44, מאת Fernando Moraes ‏< fernandosdemor...@gmail.com>: > Hello, I would like to know if it is possible to modify via config > properties the

Modify kafka-connect api context path

Hello, I would like to know if it is possible to modify via config properties the kafka-connect context path. I have a scenario where the proxy redirects a request to a connect worker using a context path. I've already looked at the source code here, and it doesn't really seem to have a point for

Kafka Stream custom join using state store

Hi, I didn't reach any people on StackOverflow, so I try here : https://stackoverflow.com/questions/67694907/kafka-stream-custom-join-using-state-store I'm really stuck on that part and I have the feeling only the Processor API can help me. But since the stream is really complex, I would prefer

Re: Weird behavior of topic retention - some are cleaned up too often, some are not at all

Thank you, Matthias, for the ideas to verify next! Here is what I see: Topic 1 - that is not being cleaned up for 3 days already, but has retention set to 4 hrs: (I've truncated the payload but left the important details): 11:32:11 confluent@qv-ckafkama7 [~] $ /usr/bin/kafka-dump-log

Re: Metadata max idle vs age ms

Anybody has any inputs on this one? Sent from my iPhone > On 25 May 2021, at 9:49 am, Neeraj Vaidya wrote: > > Hi All, (I have asked this on SO as well, but happy to paste the response > there if I get a answer here or vice-versa). > > I would like to know the impact of setting both of

Re: Weird behavior of topic retention - some are cleaned up too often, some are not at all

Kafka's retention policy is a little bit tricky, because it determines if data is subject to deletion by comparing the embedded record timestamps to the broker wall-clock time. Can you verify your record timestamps as well as broker clocks? If you write "future data", ie, data with timestamps

Re: why does kafka not use the rebalance strategy of rocketmq

As of Kafka 2.4, Kafka also supports incremental balancing and does avoid a stop-the-world effect. Cf. https://cwiki.apache.org/confluence/display/KAFKA/KIP-429%3A+Kafka+Consumer+Incremental+Rebalance+Protocol There is also a Kafka Summit talk about it: