Hey Thomas, On Fri, Nov 9, 2018 at 6:07 PM Thomas Weise <t...@apache.org> wrote: > Is there a way to activate the predefined options via configuration / flink- > conf.yaml? Or only programmatically, like in [4]? The difficulty with the > programmatic route (assuming this works now), is that in my case the client > is Beam and I'm not writing the code that submits the job.
AFAIK no. You can only do it programmatically at the moment [1]. Having the option to configure all settings through the configuration file seems to be a valid feature request to me. @Stefan Richter (cc'd): Are there any reasons that speak against exposing these options via the configuration file in your opinion? Best, Ufuk [1] Looking at the code in [2] and [3], the only options that are exposed via the configuration file are local directories and the timer service factory. [2] https://github.com/apache/flink/blob/master/flink-state-backends/flink-statebackend-rocksdb/src/main/java/org/apache/flink/contrib/streaming/state/RocksDBOptions.java [3] https://github.com/apache/flink/blob/master/flink-state-backends/flink-statebackend-rocksdb/src/main/java/org/apache/flink/contrib/streaming/state/RocksDBStateBackend.java
