GitHub user cloud-fan opened a pull request:

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

    [SPARK-18464][SQL][backport] support old table which doesn't store schema 
in table properties

    backport https://github.com/apache/spark/pull/18907 to branch 2.2

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

    $ git pull https://github.com/cloud-fan/spark backport

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

    https://github.com/apache/spark/pull/18963.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 #18963
    
----
commit 7964c9ad750fc3035042260098616bcc4698e219
Author: Wenchen Fan <[email protected]>
Date:   2017-08-15T16:04:56Z

    [SPARK-18464][SQL][FOLLOWUP] support old table which doesn't store schema 
in table properties
    
    This is a follow-up of https://github.com/apache/spark/pull/15900 , to fix 
one more bug:
    When table schema is empty and need to be inferred at runtime, we should 
not resolve parent plans before the schema has been inferred, or the parent 
plans will be resolved against an empty schema and may get wrong result for 
something like `select *`
    
    The fix logic is: introduce `UnresolvedCatalogRelation` as a placeholder. 
Then we replace it with `LogicalRelation` or `HiveTableRelation` during 
analysis, so that it's guaranteed that we won't resolve parent plans until the 
schema has been inferred.
    
    regression test
    
    Author: Wenchen Fan <[email protected]>
    
    Closes #18907 from cloud-fan/bug.

----


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to