GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/13060
[SPARK-15276][SQL] CREATE TABLE with LOCATION should imply EXTERNAL
## What changes were proposed in this pull request?
Before:
```
-- uses that location but issues a warning
CREATE TABLE my_tab LOCATION /some/path
-- deletes any existing data in the specified location
DROP TABLE my_tab
```
After:
```
-- uses that location but creates an EXTERNAL table instead
CREATE TABLE my_tab LOCATION /some/path
-- does not delete the data at /some/path
DROP TABLE my_tab
```
This patch essentially makes the `EXTERNAL` field optional.
## How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration
tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise,
remove this)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andrewor14/spark location-implies-external
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13060.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 #13060
----
commit 9507b67885cb2f1e9014e3175f35c505874e7ccf
Author: Andrew Or <[email protected]>
Date: 2016-05-11T21:16:01Z
Specifying LOCATION implies it's an EXTERNAL 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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
