You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/11 07:47:00 UTC

[jira] [Updated] (FLINK-8297) RocksDBListState stores whole list in single byte[]

     [ https://issues.apache.org/jira/browse/FLINK-8297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-8297:
----------------------------------
    Labels: pull-request-available  (was: )

> RocksDBListState stores whole list in single byte[]
> ---------------------------------------------------
>
>                 Key: FLINK-8297
>                 URL: https://issues.apache.org/jira/browse/FLINK-8297
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.3.2, 1.4.0
>            Reporter: Jan Lukavský
>            Priority: Major
>              Labels: pull-request-available
>
> RocksDBListState currently keeps whole list of data in single RocksDB key-value pair, which implies that the list actually must fit into memory. Larger lists are not supported and end up with OOME or other error. The RocksDBListState could be modified so that individual items in list are stored in separate keys in RocksDB and can then be iterated over. A simple implementation could reuse existing RocksDBMapState, with key as index to the list and a single RocksDBValueState keeping track of how many items has already been added to the list. Because this implementation might be less efficient in come cases, it would be good to make it opt-in by a construct like
> {{new RocksDBStateBackend().enableLargeListsPerKey()}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)