You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiao Li (JIRA)" <ji...@apache.org> on 2017/01/01 17:44:58 UTC
[jira] [Updated] (SPARK-19048) Managed Partitioned Table in
InMemoryCatalog: the user specified partition location is not deleted after
table dropping
[ https://issues.apache.org/jira/browse/SPARK-19048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Li updated SPARK-19048:
----------------------------
Description: The data in the managed table should be deleted after table is dropped. However, if the partition location is not under the location of the partitioned table, it is not deleted as expected. Users can specify any location for the partition when they adding a partition. (was: The data in the managed table should be deleted after table is dropped. However, if the partition location is not under the location of the partitioned table, it is not dropped as expected. Users can specify any location for the partition when they adding a partition.)
> Managed Partitioned Table in InMemoryCatalog: the user specified partition location is not deleted after table dropping
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SPARK-19048
> URL: https://issues.apache.org/jira/browse/SPARK-19048
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.2, 2.1.0
> Reporter: Xiao Li
>
> The data in the managed table should be deleted after table is dropped. However, if the partition location is not under the location of the partitioned table, it is not deleted as expected. Users can specify any location for the partition when they adding a partition.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org