GitHub user cloud-fan opened a pull request:

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

    [SPARK-18647][SQL] do not put provider in table properties for Hive serde 
table

    ## What changes were proposed in this pull request?
    
    In Spark 2.1, we make Hive serde tables case-preserving by putting the 
table metadata in table properties, like what we did for data source table. 
However, we should not put table provider, as it will break forward 
compatibility. e.g. if we create a Hive serde table with Spark 2.1, using 
`sql("create table test stored as parquet as select 1")`, we will fail to read 
it with Spark 2.0, as Spark 2.0 mistakenly treat it as data source table 
because there is a `provider` entry in table properties.
    
    Logically Hive serde table's provider is always hive, we don't need to 
store it in table properties, this PR removes it.
    
    ## How was this patch tested?
    
    manually test the forward compatibility issue.


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

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

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

    https://github.com/apache/spark/pull/16080.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 #16080
    
----
commit 89f1625b35ef21799e5d0d815dc18e23f3fd8106
Author: Wenchen Fan <wenc...@databricks.com>
Date:   2016-11-30T11:17:13Z

    do not put provider in table properties for Hive serde table

----


---
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