Hi Maciek,
Thanks for reaching out. Only through these interactions, we know how
important certain features are to users.
Queryable State has some limitations and makes the whole system rather
fragile. Most users that try it out are disappointed that there is actually
no SQL support. If we could
Hi Konstantin,
thanks for detailed answer. I also thought about CoFunction, but it is a
bit too heavy for us for the moment (each state would have to have
additional kafka producer/consumer).
Guess we'll use QueryableState for now and try to phase it out slowly...
thanks,
maciek
On
Hi Maciek,
Thank you for reaching out. I'll try to answer your questions separately.
- nothing comparable. You already mention the State Processor API. Besides
that, I can only think of a side channel (CoFunction) that is used to
request a certain state that is then send to a side output and
Hello,
We are using QueryableState in some of Nussknacker deployments as a nice
addition, allowing end users to peek inside job state for a given key
(we mostly use custom operators).
Judging by mailing list and feature radar proposition by Stephan:
