[
https://issues.apache.org/jira/browse/FLINK-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-3692:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
