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

Posted to issues@spark.apache.org by "Takeshi Yamamuro (Jira)" <ji...@apache.org> on 2020/05/07 00:03:00 UTC

[jira] [Resolved] (SPARK-31647) Deprecate 'spark.sql.optimizer.metadataOnly'

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

Takeshi Yamamuro resolved SPARK-31647.
--------------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Resolved by https://github.com/apache/spark/pull/28459

> Deprecate 'spark.sql.optimizer.metadataOnly'
> --------------------------------------------
>
>                 Key: SPARK-31647
>                 URL: https://issues.apache.org/jira/browse/SPARK-31647
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Hyukjin Kwon
>            Assignee: Hyukjin Kwon
>            Priority: Major
>             Fix For: 3.0.0
>
>
> This optimization can cause a potential correctness issue, see also SPARK-26709.
> Also, it seems difficult to extend the optimization. Basically you should whitelist all available functions.
> Seems we should rather deprecate and remove this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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