GitHub user yhuai opened a pull request:

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

    [SPARK-13454] [SQL] Allow users to drop a table with a name starting with 
an underscore.

    ## What changes were proposed in this pull request?
    
    This change adds a workaround to allow users to drop a table with a name 
starting with an underscore. Without this patch, we can create such a table, 
but we cannot drop it. The reason is that Hive's parser unquote an quoted 
identifier. So, when we issue a drop table command to Hive, a table name 
starting with an underscore is actually not quoted. Then, Hive will complain 
about it because it does not support a table name starting with an underscore 
without using backticks (underscores are allowed as long as it is not the first 
char though).
    
    ## How was this patch tested?
    
    Add a test to make sure we can drop a table with a name starting with an 
underscore.
    
    https://issues.apache.org/jira/browse/SPARK-13454


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

    $ git pull https://github.com/yhuai/spark fixDropTable

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

    https://github.com/apache/spark/pull/11349.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 #11349
    
----
commit 70cfee0f4f13225b307098eb41457fb3cb671c39
Author: Yin Huai <[email protected]>
Date:   2016-02-24T18:40:51Z

    Allow users to drop a table with a name starting with underscore.

----


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