[
https://issues.apache.org/jira/browse/FLINK-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321564#comment-17321564
]
Flink Jira Bot commented on FLINK-10372:
----------------------------------------
This issue and all of its Sub-Tasks have not been updated for 180 days. So, it
has been labeled "stale-minor". If you are still affected by this bug or are
still interested in this issue, please give an update and remove the label. In
7 days the issue will be closed automatically.
> There is no API to configure the timer state backend
> ----------------------------------------------------
>
> Key: FLINK-10372
> URL: https://issues.apache.org/jira/browse/FLINK-10372
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream, Runtime / State Backends
> Affects Versions: 1.6.0
> Reporter: Elias Levy
> Priority: Minor
> Labels: stale-minor
>
> Flink 1.6.0, via FLINK-9485, introduced the option to store timers in RocksDB
> instead of the heap. Alas, this can only be configured via the
> {{state.backend.rocksdb.timer-service.factory}} config file option. That
> means that the choice of state backend to use for timer can't be made on a
> per job basis on a shared cluster.
> There is a need for an API in {{RocksDBStateBackend}} to configure the
> backend per job.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
