You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/09/07 00:07:00 UTC
[jira] [Commented] (SPARK-21835) RewritePredicateSubquery should
not produce unresolved query plans
[ https://issues.apache.org/jira/browse/SPARK-21835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156226#comment-16156226 ]
Apache Spark commented on SPARK-21835:
--------------------------------------
User 'viirya' has created a pull request for this issue:
https://github.com/apache/spark/pull/19151
> RewritePredicateSubquery should not produce unresolved query plans
> ------------------------------------------------------------------
>
> Key: SPARK-21835
> URL: https://issues.apache.org/jira/browse/SPARK-21835
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Liang-Chi Hsieh
> Assignee: Liang-Chi Hsieh
> Fix For: 2.3.0
>
>
> {{RewritePredicateSubquery}} rewrites correlated subquery to join operations. During the structural integrity, I found {[RewritePredicateSubquery}} can produce unresolved query plans due to conflicting attributes. We should not let {{RewritePredicateSubquery}} produce unresolved plans.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org