Filed https://issues.apache.org/jira/browse/KAFKA-16295
Also, for global store support, we do have a ticket already:
https://issues.apache.org/jira/browse/KAFKA-13523
It's actually a little bit more involved due to position tracking... I
guess we might need a KIP to fix this.
And yes: if
riginal Message-
> From: Sophie Blee-Goldman
> Sent: Wednesday, November 22, 2023 1:51 AM
> To: christian.zueg...@ams-osram.com.invalid
> Cc: users@kafka.apache.org
> Subject: Re: GlobalKTable with RocksDB - queries before state RUNNING?
>
> [Sie erhalten nicht häufig E-Mai
ueg...@ams-osram.com.invalid
Cc: users@kafka.apache.org
Subject: Re: GlobalKTable with RocksDB - queries before state RUNNING?
[Sie erhalten nicht häufig E-Mails von sop...@responsive.dev. Weitere
Informationen, warum dies wichtig ist, finden Sie unter
https://aka.ms/LearnAboutSenderIdentification ]
Just to
Just to make sure I understand the logs, you're saying the "new file
processed" lines represent store queries, and presumably the
com.osr.serKafkaStreamsService is your service that's issuing these queries?
You need to wait for the app to finish restoring state before querying it.
Based on this
Hi,
we have the following problem - a Kafka Topic ~20Megabytes is made available as
GlobalKTable for queries. With using RocksDB the GKTable is ready for queries
instantly even without having reading the data complete - all get() requests
return null. After a few seconds the data is querieable
