From what I've read, a Ktable directly sourced from a compacted topic is smart
enough to not use a change log in the background. I must be doing something
wrong though as I have a setup similar to below and I can see on the broker a
topic named something like myappid-myStore-changelog is actual
Log compaction though allows it to work as a data store quite well for some use
cases . It's exactly why I started looking hard at Kafka lately.
"The general idea is quite simple. Rather than maintaining only recent
log entries in the log and throwing away old log segments we maintain
the most
