Open cedw93 opened 5 years ago
Thanks for reporting this issue @cedw93 . I looked at the code, and we certainly don't cache the topic list anywhere. This isn't expected behavior. Are you seeing this consistently, even after a very long period of time passes? What may be happening is that since kafka topic creation is not synchronous, your KSQL client may be hitting a broker which doesn't have the updated metadata yet, and hence returns stale data. But the window where this happens should be very small.
When running a
SHOW TOPICS;
command in ksql I expect to see the true list of the currently defined Kafka topicsIf I start my ksql client and run
SHOW TOPICS;
I get a list of topics like so;this matches the expected output as I have the following topics in kafka topics in kafka:
The problem comes when I create new topics. I created a new topic in Kafka called
ksqlTest
which I then expected it to show in the ksql output. But this is not the case:Kafka topics:
ksql output
You can see the topic
ksqlTest
is missing from this output (and the __ ones are but I expect that's intended).This also applies if I create more topics the
SHOW TOPICS;
output never seems to update to include the new topics. It doesn't seem to ever update from its initial list.Is this a problem or is this intended behavior? Is there a way to always ensure the correct list of topics in return.
ksql properties:
I also have SASL SCRAM with the JAAS config configured which seems to be working as it does manage to get the topic list at least once correctly.