[
https://issues.apache.org/jira/browse/FLINK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-10121:
-----------------------------------
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.
> Introduce methods to remove registered operator states
> ------------------------------------------------------
>
> Key: FLINK-10121
> URL: https://issues.apache.org/jira/browse/FLINK-10121
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Stefan Richter
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> User can register new operator states but never remove a registered state.
> This is particularly problematic with expensive states or states that we
> register only to provide backwards compatibility. We can also consider the
> same for keyed state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
