You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2020/08/07 07:37:00 UTC
[jira] [Resolved] (SPARK-32528) The analyze method should make sure
the plan is analyzed
[ https://issues.apache.org/jira/browse/SPARK-32528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-32528.
---------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
Issue resolved by pull request 29349
[https://github.com/apache/spark/pull/29349]
> The analyze method should make sure the plan is analyzed
> --------------------------------------------------------
>
> Key: SPARK-32528
> URL: https://issues.apache.org/jira/browse/SPARK-32528
> Project: Spark
> Issue Type: Test
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Wenchen Fan
> Assignee: Wenchen Fan
> Priority: Minor
> Fix For: 3.1.0
>
>
> In tests, we usually call `plan.analyze` to get the analyzed plan and test analyzer/optimizer rules. However, `plan.analyze` doesn't guarantee the plan is resolved, which may surprise the test writers.
--
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