[
https://issues.apache.org/jira/browse/SPARK-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859398#comment-15859398
]
Nattavut Sutyanyong edited comment on SPARK-18874 at 2/9/17 11:49 AM:
----------------------------------------------------------------------
Thank you, [~hvanhovell], [~dkbiswal], for reviewing the design document. I
have attached the revised version as a pdf format in this JIRA. [~rxin]: FYI.
We will be submitting a PR for the code by Tuesday February 14.
P.S. We will submit the last test PR today (Feb 9). As of now, there are 4
pending test PRs waiting for review. We hope to have all the test PRs merged
before the code. This way when the code is merged, we can verify by exercising
the new code against those test cases.
was (Author: nsyca):
Thank you, [~hvanhovell][~dkbiswal], for reviewing the design document. I have
attached the revised version as a pdf format in this JIRA. [~rxin]: FYI.
We will be submitting a PR for the code by Tuesday February 14.
P.S. We will submit the last test PR today (Feb 9). As of now, there are 4
pending test PRs waiting for review. We hope to have all the test PRs merged
before the code. This way when the code is merged, we can verify by exercising
the new code against those test cases.
> First phase: Deferring the correlated predicate pull up to Optimizer phase
> --------------------------------------------------------------------------
>
> Key: SPARK-18874
> URL: https://issues.apache.org/jira/browse/SPARK-18874
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Nattavut Sutyanyong
> Attachments: SPARK-18874-3.pdf
>
>
> This JIRA implements the first phase of SPARK-18455 by deferring the
> correlated predicate pull up from Analyzer to Optimizer. The goal is to
> preserve the current functionality of subquery in Spark 2.0 (if it works, it
> continues to work after this JIRA, if it does not, it won't). The performance
> of subquery processing is expected to be at par with Spark 2.0.
> The representation of the LogicalPlan after Analyzer will be different after
> this JIRA that it will preserve the original positions of correlated
> predicates in a subquery. This new representation is a preparation work for
> the second phase of extending the support of correlated subquery to cases
> Spark 2.0 does not support such as deep correlation, outer references in
> SELECT clause.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
