[jira] [Commented] (FLINK-8189) move flink-statebackend-rocksdb out of flink-contrib

2018-01-26 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann commented on FLINK-8189:
--

Hi [~phoenixjiangnan], I agree with [~Zentol] that we should continue the 
discussion in FLINK-4602. There it was actually stated that it might be 
problematic to bundle RocksDB with {{flink-runtime}} because of licensing 
concerns.

> move flink-statebackend-rocksdb out of flink-contrib
> 
>
> Key: FLINK-8189
> URL: https://issues.apache.org/jira/browse/FLINK-8189
> Project: Flink
>  Issue Type: Sub-task
>  Components: State Backends, Checkpointing
>Affects Versions: 1.5.0
>Reporter: Bowen Li
>Assignee: Bowen Li
>Priority: Major
>
> Move {{flink-statebackend-rocksdb}} into probably its own/state-backend 
> module or {{flink-runtime}} package.
> A few reasons:
> * RocksDB state backend has been evolving into the standard state backends 
> because it can handle much larger state compared to HeapStateBackend. It 
> would be better to put it into /lib package in Flink somehow by default
> * {{flink-contrib}} doesn't show the correct package hierarchy



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

[jira] [Commented] (FLINK-8189) move flink-statebackend-rocksdb out of flink-contrib

2018-01-25 Thread Chesnay Schepler (JIRA) 

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

Chesnay Schepler commented on FLINK-8189:
-

I'm tempted to close this as "Won't fix"/"Duplicate" due to the discussion in 
FLINK-4602.

> move flink-statebackend-rocksdb out of flink-contrib
> 
>
> Key: FLINK-8189
> URL: https://issues.apache.org/jira/browse/FLINK-8189
> Project: Flink
>  Issue Type: Sub-task
>  Components: State Backends, Checkpointing
>Affects Versions: 1.5.0
>Reporter: Bowen Li
>Assignee: Bowen Li
>Priority: Major
>
> Move {{flink-statebackend-rocksdb}} into probably its own/state-backend 
> module or {{flink-runtime}} package.
> A few reasons:
> * RocksDB state backend has been evolving into the standard state backends 
> because it can handle much larger state compared to HeapStateBackend. It 
> would be better to put it into /lib package in Flink somehow by default
> * {{flink-contrib}} doesn't show the correct package hierarchy



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

[jira] [Commented] (FLINK-8189) move flink-statebackend-rocksdb out of flink-contrib

2018-01-25 Thread Bowen Li (JIRA) 

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

Bowen Li commented on FLINK-8189:
-

[~till.rohrmann] [~aljoscha] [~srichter] Hi guys, I'm thinking of start this 
task since we've finished removing {{flink-contrib/flink-streaming-contrib}}. 

I'm leaning towards moving {{flink-statebackend-rocksdb}} into 
{{flink-runtime}} so that it can sit with {{HeapStateBackend}}.

What do you think?

> move flink-statebackend-rocksdb out of flink-contrib
> 
>
> Key: FLINK-8189
> URL: https://issues.apache.org/jira/browse/FLINK-8189
> Project: Flink
>  Issue Type: Sub-task
>  Components: State Backends, Checkpointing
>Affects Versions: 1.5.0
>Reporter: Bowen Li
>Assignee: Bowen Li
>Priority: Major
>
> Move {{flink-statebackend-rocksdb}} into probably its own/state-backend 
> module or {{flink-runtime}} package.



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