ce as that is on-heap and
>>> lightweight.
>>>
>>> Best
>>> Yun Tang
>>> --
>>> *From:* Robin Cassan
>>> *Sent:* Friday, May 15, 2020 20:59
>>> *To:* Yun Tang
>>> *Cc:* user
>>>
u do not have
>> many key-by keys, operator state is a good choice as that is on-heap and
>> lightweight.
>>
>> Best
>> Yun Tang
>> --
>> *From:* Robin Cassan
>> *Sent:* Friday, May 15, 2020 20:59
>> *To:* Yun Tang
>
ent:* Friday, May 15, 2020 20:59
> *To:* Yun Tang
> *Cc:* user
> *Subject:* Re: Protection against huge values in RocksDB List State
>
> Hi Yun, thanks for your answer! And sorry I didn't see this limitation
> from the documentation, makes sense!
> In our case, we are mer
Yun Tang
From: Robin Cassan
Sent: Friday, May 15, 2020 20:59
To: Yun Tang
Cc: user
Subject: Re: Protection against huge values in RocksDB List State
Hi Yun, thanks for your answer! And sorry I didn't see this limitation from the
documentation, makes sens
040/java/src/main/java/org/rocksdb/RocksDB.java#L1382
>
> Best
> Yun Tang
> --
> *From:* Robin Cassan
> *Sent:* Friday, May 15, 2020 0:37
> *To:* user
> *Subject:* Protection against huge values in RocksDB List State
>
> Hi all!
&
/50d63a2af01a46dd938dc1b717067339c92da040/java/src/main/java/org/rocksdb/RocksDB.java#L1382
Best
Yun Tang
From: Robin Cassan
Sent: Friday, May 15, 2020 0:37
To: user
Subject: Protection against huge values in RocksDB List State
Hi all!
I cannot seem to find any
Hi all!
I cannot seem to find any setting to limit the number of records appended
in a RocksDBListState that is used when we use SessionWindows with a
ProcessFunction.
It seems that, for each incoming element, the new element will be appended
to the value with the RocksDB `merge` operator, without
