Thanks for pointing out Satish. Links updated:
Hello Kafka users, developers and client-developers,
This is the third candidate for release of Apache Kafka 1.1.0.
This is minor version release of Apache Kakfa. It Includes 29 new KIPs.
Please see the
Hello!
I've read about the KSQL streaming SQL for Kafka. In my opinion, this is a
big step for performing complex event processing on streams.
In the provides examples there is a TUMBLING window function.
By default, I assume that the windowing is performed on the timestamp
generated by the sys
Hi,
A changelog would have infinite retention(only one can be specified among
compact or delete), howsover while using windows store, we have
timewindows.until() which specifies the retention.
A KTable can be created using TimeWindows.until(), does that mean that
changelog would have retention as
Hi All,
Just found the answer to this, a changelog topic can now have both delete
and compact as clean up policy. Also, a retention period can also be set.
So, in case of window store, whatever we specify as until becomes the
retention.ms of the changelog topic.
-Sameer.
On Wed, Mar 14, 2018 at
Hi Florin,
just want to point out that KSQL is not part of Apache Kafka and you
might ask your questions on Confluent Google Group instead:
https://groups.google.com/forum/#!forum/confluent-platform
To answer your question: by default KSQL uses the record embedded
metadata timestamp for tumbling
Below is a simple kafka producer code. The bootstrap.servers address
100.67.148.133:8080is a Virtual IP and translates to a real broker server
IP/port: 11.180.140.172:9092.
After I sent the request, the Virtual IP successfully sent back topic
VIP_test1's metadata. (see wireshark screen capture).