[
https://issues.apache.org/jira/browse/FLINK-10912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16698961#comment-16698961
]
Stefan Richter commented on FLINK-10912:
----------------------------------------
[~thw] Is this something that you would like to contribute? Then I would offer
support if there are questions about the design and I can also review the
changes. In general, I think the fastest change would be to have the options
factory configurable from the flink conf. Alternatively or on top of that, we
could also consider to mirror and expose all RocksDB options as config keys.
> 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
> Priority: Major
>
> 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)
