[ 
https://issues.apache.org/jira/browse/HIVE-23467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sam An updated HIVE-23467:
--------------------------
    Description: 
We have an auto.purge flag, which means skip trash. It can be confusing as we 
have 'external.table.purge'='true' to indicate delete table data when this 
tblproperties is set. 

We should make the meaning clearer by introducing a skip trash alias/option. 

Additionally, we shall add an alias for external.table.purge, and name it 
external.table.autodelete, and document it more prominently, so as to maintain 
backward compatibility, and make the meaning of auto deletion of data more 
obvious. 

The net effect of these 2 changes will be. If the user sets 

'external.table.autodelete'='true'

the table data will be removed when table is dropped. and if 

'skip.trash'='true' 

is set, HMS will not move the table data to trash folder when removing the 
files. This will result in faster removal, especially when underlying FS is S3. 

  was:
We have an auto.purge flag, which means skip trash. It can be confusing as we 
have 'external.table.purge'='true' to indicate delete table data when this 
tblproperties is set. 

 

We should make the meaning clearer by introducing a skip trash alias/option. 


> Add a skip.trash config for HMS to skip trash when deleting external table 
> data
> -------------------------------------------------------------------------------
>
>                 Key: HIVE-23467
>                 URL: https://issues.apache.org/jira/browse/HIVE-23467
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive
>            Reporter: Sam An
>            Assignee: Sam An
>            Priority: Trivial
>
> We have an auto.purge flag, which means skip trash. It can be confusing as we 
> have 'external.table.purge'='true' to indicate delete table data when this 
> tblproperties is set. 
> We should make the meaning clearer by introducing a skip trash alias/option. 
> Additionally, we shall add an alias for external.table.purge, and name it 
> external.table.autodelete, and document it more prominently, so as to 
> maintain backward compatibility, and make the meaning of auto deletion of 
> data more obvious. 
> The net effect of these 2 changes will be. If the user sets 
> 'external.table.autodelete'='true'
> the table data will be removed when table is dropped. and if 
> 'skip.trash'='true' 
> is set, HMS will not move the table data to trash folder when removing the 
> files. This will result in faster removal, especially when underlying FS is 
> S3. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to