[
https://issues.apache.org/jira/browse/FLINK-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328944#comment-17328944
]
Flink Jira Bot commented on FLINK-3692:
---------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Develop a Kafka state backend
> -----------------------------
>
> Key: FLINK-3692
> URL: https://issues.apache.org/jira/browse/FLINK-3692
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / State Backends
> Reporter: Elias Levy
> Priority: Major
> Labels: stale-major
>
> Flink clusters usually consume of a Kafka cluster. It simplify operations if
> Flink could store its state checkpoints in Kafka. This should be possibly
> using different topics to write to, partitioning appropriately, and using
> compacted topics. This would avoid the need to run an HDFS cluster just to
> store Flink checkpoints.
> For inspiration you may want to take a look at how Samza checkpoints a task's
> local state to a Kafka topic, and how the newer Kafka consumers checkpoint
> their offsets to Kafka.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
