[jira] [Updated] (FLINK-32476) Support configuring object-reuse for internal operators
[ https://issues.apache.org/jira/browse/FLINK-32476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32476: --- Labels: auto-deprioritized-major pull-request-available (was: pull-request-available stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days 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. > Support configuring object-reuse for internal operators > --- > > Key: FLINK-32476 > URL: https://issues.apache.org/jira/browse/FLINK-32476 > Project: Flink > Issue Type: New Feature > Components: Runtime / Task >Reporter: Xuannan Su >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available > > Currently, object reuse is disabled by default for streaming jobs in order to > prevent unexpected behavior. Object reuse becomes problematic when the > upstream operator stores its output while the downstream operator modifies > the input. > However, many operators implemented by Flink, such as Flink SQL operators, do > not modify the input. This implies that it is safe to reuse the input object > in such cases. Therefore, we intend to enable object reuse specifically for > operators that do not modify the input. > As the first step, we will focus on the operators implemented within Flink. > We will create the FLIP to introduce the API that allows user-defined > operators to enable object reuse in the future. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-32476) Support configuring object-reuse for internal operators
[ https://issues.apache.org/jira/browse/FLINK-32476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-32476: --- Labels: pull-request-available stale-major (was: pull-request-available) 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 60 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. > Support configuring object-reuse for internal operators > --- > > Key: FLINK-32476 > URL: https://issues.apache.org/jira/browse/FLINK-32476 > Project: Flink > Issue Type: New Feature > Components: Runtime / Task >Reporter: Xuannan Su >Priority: Major > Labels: pull-request-available, stale-major > > Currently, object reuse is disabled by default for streaming jobs in order to > prevent unexpected behavior. Object reuse becomes problematic when the > upstream operator stores its output while the downstream operator modifies > the input. > However, many operators implemented by Flink, such as Flink SQL operators, do > not modify the input. This implies that it is safe to reuse the input object > in such cases. Therefore, we intend to enable object reuse specifically for > operators that do not modify the input. > As the first step, we will focus on the operators implemented within Flink. > We will create the FLIP to introduce the API that allows user-defined > operators to enable object reuse in the future. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (FLINK-32476) Support configuring object-reuse for internal operators
[ https://issues.apache.org/jira/browse/FLINK-32476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-32476: --- Labels: pull-request-available (was: ) > Support configuring object-reuse for internal operators > --- > > Key: FLINK-32476 > URL: https://issues.apache.org/jira/browse/FLINK-32476 > Project: Flink > Issue Type: New Feature > Components: Runtime / Task >Reporter: Xuannan Su >Priority: Major > Labels: pull-request-available > > Currently, object reuse is disabled by default for streaming jobs in order to > prevent unexpected behavior. Object reuse becomes problematic when the > upstream operator stores its output while the downstream operator modifies > the input. > However, many operators implemented by Flink, such as Flink SQL operators, do > not modify the input. This implies that it is safe to reuse the input object > in such cases. Therefore, we intend to enable object reuse specifically for > operators that do not modify the input. > As the first step, we will focus on the operators implemented within Flink. > We will create the FLIP to introduce the API that allows user-defined > operators to enable object reuse in the future. -- This message was sent by Atlassian Jira (v8.20.10#820010)
