Thanks. I was curious about the other real world use cases i.e what do people
use it for ? Is this widely used or mostly for debugging purposes ? Any caveats
?
Thanks
Mohan
On 10/1/20, 5:55 PM, "Guozhang Wang" wrote:
Mohan,
I think you can build a REST API on top of app1 direct
I am looking for some official statement that OpenJDK is supported for Kafka,
in particular 2.5.0.
I know that it works, but I need to “prove” it to a customer. Is there any
document or release note I can point to?
Mohan,
I think you can build a REST API on top of app1 directly leveraging on its
IQ interface. For some examples code you can refer to
https://github.com/confluentinc/kafka-streams-examples/tree/6.0.0-post/src/main/java/io/confluent/examples/streams/interactivequeries
Guozhang
On Thu, Oct 1, 20
Hi,
You can use kafka connect to export topic data to external systems.
https://docs.confluent.io/3.1.1/connect/connect-jdbc/docs/sink_connector.html
Thanks,
Akhilesh Pathodia
On Thu, Oct 1, 2020 at 7:29 AM Spectrum lib wrote:
> Hi All,
> I am using the Kafka version kafka_2.12-2.4.0. I have
Hi Guozhang,
The async event trigger process is not running as a kafka streams application.
It offers REST interface where other applications post events which in turn
needs to go through App1's state and send requests to App2 via Kafka. Here is
the diagram:
KafkaTopics---> App1 ---> App2
Hi All,
I am using the Kafka version kafka_2.12-2.4.0. I have 1 Kafka broker.
I am having a topic with 1 partition.How can i push topic data in the
MsSQL Database using any language Java,C# etc.
Thank You in advance
I was also facing the same problem. I was using "replication.latency.ms"
jmx metric which does not get reset.
I started using "replication.latency.avg" which resets when there is no new
message to replicate.
On Thu, Oct 1, 2020, 7:06 PM Shiva Sagar Reddy Veeram
wrote:
> I’ve noticed the replica
I’ve noticed the replication latencies are not reset when the destination
topic is all caught up and there is no more data to replicate. So polling
metrics after still returns the last replication latency that was recorded when
there was data. Is there a way to reset the metrics once replicatio
