flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "aitozi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10098) Programmatically select timer storage backend
Date Mon, 27 May 2019 16:58:01 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849082#comment-16849082
] 

aitozi commented on FLINK-10098:
--------------------------------

I will work on this issue to solve the problem

> Programmatically select timer storage backend
> ---------------------------------------------
>
>                 Key: FLINK-10098
>                 URL: https://issues.apache.org/jira/browse/FLINK-10098
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination, Runtime / State Backends
>    Affects Versions: 1.6.0, 1.7.0
>            Reporter: Elias Levy
>            Assignee: aitozi
>            Priority: Major
>
> FLINK-9486 introduced timer storage on the RocksDB storage backend.  Right now it is
only possible to configure RocksDB as the storage for timers by settings the {{state.backend.rocksdb.timer-service.factory}}
value in the configuration file for Flink.
> As the state storage backend can be programmatically selected by by jobs via  {{env.setStateBackend(...)}},
the timer backend should also be configurable programmatically.
> Different jobs should be able to store their timers in different storage backends.



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

Mime
View raw message