[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ 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-deprioritized-major auto-deprioritized-minor auto-unassigned (was: auto-deprioritized-major auto-unassigned stale-minor) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor, > auto-unassigned > > 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.20.1#820001)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ 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-deprioritized-major auto-unassigned stale-minor (was: auto-deprioritized-major 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 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. > 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: Minor > Labels: auto-deprioritized-major, auto-unassigned, stale-minor > > 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.20.1#820001)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ 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-deprioritized-major auto-unassigned (was: auto-unassigned stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > 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: Minor > Labels: auto-deprioritized-major, auto-unassigned > > 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)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ 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)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ 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 (was: stale-assigned) > 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 >Assignee: Stefan Richter >Priority: Major > Labels: auto-unassigned > > 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)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ https://issues.apache.org/jira/browse/FLINK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-10121: --- Labels: stale-assigned (was: ) > 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 >Assignee: Stefan Richter >Priority: Major > Labels: stale-assigned > > 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)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ https://issues.apache.org/jira/browse/FLINK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann updated FLINK-10121: -- Fix Version/s: (was: 1.7.0) > 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: State Backends, Checkpointing >Reporter: Stefan Richter >Assignee: Stefan Richter >Priority: Major > Fix For: 1.8.0 > > > 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 (v7.6.3#76005)
[jira] [Updated] (FLINK-10121) Introduce methods to remove registered operator states
[ https://issues.apache.org/jira/browse/FLINK-10121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Till Rohrmann updated FLINK-10121: -- Fix Version/s: 1.8.0 > 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: State Backends, Checkpointing >Reporter: Stefan Richter >Assignee: Stefan Richter >Priority: Major > Fix For: 1.7.0, 1.8.0 > > > 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 (v7.6.3#76005)