[jira] [Assigned] (SPARK-45660) Re-use Literal objects when replacing timestamps in the ComputeCurrentTime rule

["Max Gekk (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-45660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Gekk reassigned SPARK-45660:
--------------------------------

    Assignee: Jan-Ole Sasse

> Re-use Literal objects when replacing timestamps in the ComputeCurrentTime rule
> -------------------------------------------------------------------------------
>
>                 Key: SPARK-45660
>                 URL: https://issues.apache.org/jira/browse/SPARK-45660
>             Project: Spark
>          Issue Type: Improvement
>          Components: Optimizer
>    Affects Versions: 3.5.0
>            Reporter: Jan-Ole Sasse
>            Assignee: Jan-Ole Sasse
>            Priority: Minor
>              Labels: pull-request-available
>
> The ComputeCurrentTime optimizer rule does produce unique timestamp Literals for current time expressions of a query. For CurrentDate and LocalTimestamp objects only the literal objects are not re-used though, but equal objects are created for each instance. This can cost unnecessary much memory in case there are many such Literal objects.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org