[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-21027:
---
Labels: auto-deprioritized-major auto-unassigned pull-request-available
(was: auto-deprioritized-major auto-unassigned)
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Assignee: Yun Tang
>Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned,
> pull-request-available
> Fix For: 1.15.0
>
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Tang updated FLINK-21027:
-
Fix Version/s: 1.15.0
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Assignee: Yun Tang
>Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
> Fix For: 1.15.0
>
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21027:
---
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.
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21027:
---
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.
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Priority: Major
> Labels: auto-unassigned, stale-major
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21027:
---
Labels: auto-unassigned (was: stale-assigned)
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Assignee: Yun Tang
>Priority: Major
> Labels: auto-unassigned
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21027:
---
Labels: stale-assigned (was: )
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Assignee: Yun Tang
>Priority: Major
> Labels: stale-assigned
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-21027) Add isStateKeyValueSerialized() method to KeyedStateBackend interface
[
https://issues.apache.org/jira/browse/FLINK-21027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-21027:
Summary: Add isStateKeyValueSerialized() method to KeyedStateBackend
interface (was: Add isKeyValueImmutable() method to KeyedStateBackend
interface)
> Add isStateKeyValueSerialized() method to KeyedStateBackend interface
> -
>
> Key: FLINK-21027
> URL: https://issues.apache.org/jira/browse/FLINK-21027
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
>Reporter: Jark Wu
>Priority: Major
>
> In Table/SQL operators, we have some optimizations that reuse objects of keys
> and records. For example, we buffer input records in {{BytesMultiMap}} and
> use the reused object to map to the underlying memory segment to reduce bytes
> copy.
> However, if we put the reused key and value into Heap statebackend, the
> result will be wrong, because it is not allowed to mutate keys and values in
> Heap statebackend.
> Therefore, it would be great if {{KeyedStateBackend}} can expose such API, so
> that Table/SQL can dynamically decide whether to copy the keys and values
> before putting into state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
