[ https://issues.apache.org/jira/browse/FLINK-10040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-10040: ----------------------------------- Labels: auto-unassigned stale-major (was: auto-unassigned) 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 Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized. > Decompose RocksDBKeyedStateBackend > ---------------------------------- > > Key: FLINK-10040 > URL: https://issues.apache.org/jira/browse/FLINK-10040 > Project: Flink > Issue Type: Improvement > Components: Runtime / State Backends > Reporter: Stefan Richter > Priority: Major > Labels: auto-unassigned, stale-major > > Over time, the class {{RocksDBKeyedStateBackend}} has grown to around 3000 > LOC, with a lot of inner classes (different checkpoint/restore strategies, > iterators, etc). > I suggest to decompose it and improve how dependencies to the classes are > provided in construction, so that things become better to maintain, extend, > and test. > Will break down this work into multiple tasks, ordered by estimated > difficulty/time required. -- This message was sent by Atlassian Jira (v8.3.4#803005)