You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (JIRA)" <ji...@apache.org> on 2016/02/07 21:00:40 UTC

[jira] [Commented] (FLINK-3358) Create constructors for FsStateBackend in RocksDBBackens

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

Gyula Fora commented on FLINK-3358:
-----------------------------------

I think this is a good idea but I am not completely sure about the default behaviour whether it should be HDFS. I would assume memory backend would be similarly frequent.

We can probably have the single string constructor backed by file state backend, or the other possibility would be to add static methods like:

RocksDBBackend.withMemoryBackend(Path)
RocksDBBackend.withFsStateBackend(Path)

What do you think?

> Create constructors for FsStateBackend in RocksDBBackens
> --------------------------------------------------------
>
>                 Key: FLINK-3358
>                 URL: https://issues.apache.org/jira/browse/FLINK-3358
>             Project: Flink
>          Issue Type: Improvement
>          Components: te backends
>    Affects Versions: 1.0.0
>            Reporter: Stephan Ewen
>            Priority: Critical
>             Fix For: 1.0.0
>
>
> I think no user understands what they are supposed to do when they should define a "backing state backend".
> The most common thing will probably be that the RocksDB snapshots are backed up to HDFS and that this is also the backing state backend.
> A simple constructor with a single URI/Path/String that configures both at the same time should be added, to make this accessible to users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)