[
https://issues.apache.org/jira/browse/FLINK-13803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17323197#comment-17323197
]
Flink Jira Bot commented on FLINK-13803:
----------------------------------------
This issue is assigned but has not received an update in 7 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Introduce SpillableHeapKeyedStateBackend and all necessities
> ------------------------------------------------------------
>
> Key: FLINK-13803
> URL: https://issues.apache.org/jira/browse/FLINK-13803
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / State Backends
> Reporter: Yu Li
> Assignee: PengFei Li
> Priority: Major
> Labels: stale-assigned
>
> This JIRA aims at introducing a new {{SpillableHeapKeyedStateBackend}} which
> will reuse most code of the {{HeapKeyedStateBackend}} (probably the only
> difference is the spill-able one will register a {{HybridStateTable}}), and
> allow using it in {{FsStateBackend}} and {{MemoryStateBackend}} (only as an
> option, by default still {{HeapKeyedStateBackend}}) through configuration.
> The related necessities include but are not limited to:
> * A relative backend builder class
> * Relative restore operation classes
> * Necessary configurations for using spill-able backend
> This should be the last JIRA after which the spill-able heap backend feature
> will become runnable regardless of the stability and performance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
