Indeed, I noticed that now. Then it should be fairly simple, if you find it
reasonable too.
> On 24 Jan 2017, at 14:20, Aljoscha Krettek wrote:
>
> Just a bit of clarification, the OperatorState stuff is independent of
> keyed state backends, i.e. even if you use RocksDB the operator state will
Just a bit of clarification, the OperatorState stuff is independent of
keyed state backends, i.e. even if you use RocksDB the operator state will
not be stored in RocksDB, only keyed state is stored there.
Right now, when an operator state (ListState) is empty we will still write
some meta data ab
Sure Till,
I would love to also make the patch but need to prioritize some other things
these days.
At least I will dig and see how complex this is regarding the different
backends.
I also have some follow-up questions, in case anybody has thought about these
things already (or is simply int
Sure Till,
I would love to also make the patch but need to prioritize some other
things these days.
At least I will dig and see how complex this is regarding the different
backends.
I also have some follow-up questions, in case anybody has thought about
these things already (or is simply interest
Hi Paris,
if there is no such issue open, then please open one so that we can track
the issue. If you have time to work on that even better :-)
Cheers,
Till
On Tue, Jan 24, 2017 at 10:25 AM, Paris Carbone wrote:
> Any thoughts/plans?
> So should I open a Jira and add this?
>
> Paris
>
> On Jan
Any thoughts/plans?
So should I open a Jira and add this?
Paris
On Jan 21, 2017, at 5:17 PM, Paris Carbone
mailto:par...@kth.se>> wrote:
Thank you for the answer Ufuk!
To elaborate a bit more, I am not using keyed state, it would be indeed tricky
in that case to discard everything.
I need th
Thank you for the answer Ufuk!
To elaborate a bit more, I am not using keyed state, it would be indeed tricky
in that case to discard everything.
I need that for operator state, in my loop fault tolerance PR [1]. The idea is
to tag a ListState (upstream log) per snapshot id.
When a concurent s
Hey Paris!
As far as I know it's not possible at the moment and not planned. Does
not sound to hard to add though. @Stefan: correct?
You can currently only clear the state via #clear in the scope of the
key for keyed state or the whole operator when used with operator
state. In case of keyed stat
Hi folks,
I have a little question regarding the managed store operator backend, in case
someone can help.
Is there some convenient way (planned or under development) to completely
unregister a state entry (e.g. a ListState) with a given id from the backend?
It is fairly easy to register new s
