GitHub user maropu opened a pull request:

    https://github.com/apache/spark/pull/18857

    [SPARK-20963][SQL][FOLLOW-UP] Use UnresolvedSubqueryColumnAliases for 
visitTableName

    ## What changes were proposed in this pull request?
    This pr (follow-up of #18772) used `UnresolvedSubqueryColumnAliases` for 
`visitTableName` in `AstBuilder`, which is a new unresolved `LogicalPlan` 
implemented in #18185.
    
    ## How was this patch tested?
    Existing tests
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/maropu/spark SPARK-20963-FOLLOWUP

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/18857.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #18857
    
----
commit 93d5b2402ba2c010b6dc425ee6eb7024b002381d
Author: Takeshi Yamamuro <yamam...@apache.org>
Date:   2017-07-31T14:30:49Z

    Use UnresolvedSubqueryColumnAliases for visitTableName

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to