You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Jiaan Geng (Jira)" <ji...@apache.org> on 2025/02/16 09:30:00 UTC

[jira] [Resolved] (SPARK-51222) Optimize ReplaceCurrentLike rule

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

Jiaan Geng resolved SPARK-51222.
--------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Issue resolved by pull request 49963
[https://github.com/apache/spark/pull/49963]

> Optimize ReplaceCurrentLike rule
> --------------------------------
>
>                 Key: SPARK-51222
>                 URL: https://issues.apache.org/jira/browse/SPARK-51222
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 4.0.0
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> ReplaceCurrentLike eagerly queries the catalog manager to get the current namespace to resolve current_database(), current catalog to resolve current_catalog().  This can be optimized to do only do this, if the plan has those expressions.



--
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