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/01/28 10:19:00 UTC
[jira] [Updated] (FLINK-10912) Configurable RocksDBStateBackend
options factory
[ https://issues.apache.org/jira/browse/FLINK-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-10912:
-----------------------------------
Labels: pull-request-available (was: )
> Configurable RocksDBStateBackend options factory
> ------------------------------------------------
>
> Key: FLINK-10912
> URL: https://issues.apache.org/jira/browse/FLINK-10912
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Affects Versions: 1.7.0
> Reporter: Thomas Weise
> Assignee: Yun Tang
> Priority: Major
> Labels: pull-request-available
>
> RocksDB has a ton of configuration options and users should be able to reach those, when necessary. Currently there are a few predefined configurations that can be activated programmatically [1] [2]. This requires change to the pipeline construction code that's hard or impossible when using higher level API or frameworks such as Apache Beam. It would be good to support an options factory that can be specified as part of the state backend configuration in flink-conf.yaml.
> [1] https://github.com/apache/flink/blob/release-1.5/flink-state-backends/flink-statebackend-rocksdb/src/main/java/org/apache/flink/contrib/streaming/state/PredefinedOptions.java#L44
> [2] https://stackoverflow.com/questions/44819521/how-to-set-rocksdbstatebackend-parameter-in-flink
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)