[
https://issues.apache.org/jira/browse/HIVE-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976374#comment-13976374
]
Xuefu Zhang commented on HIVE-6469:
-----------------------------------
{quote}
set hive.warehouse.data.skipTrash = true – explicitly set
drop table large10TBTable – this will skip trash
drop table anyOtherTable – this will skip trash
set hive.warehouse.data.skipTrash = false – if you forget this, it will
skipTrash forever, until corrected.
drop table regularTable – this will start placing data in trash
{quote}
Actually I mean hive.warehouse.data.skipTrash to be an admin property that
normal user will be able to set. Thus, the server will have this either on or
off. I expect a prod server will have this on while a dev server will have this
off. Isn't this good enough? Setting this on/off based on prod/dev seems more
reasonable than on table size. If you are in a dev environment, you just
disable the feature and why do you care whether the table is big or small. In a
prod environment, on the other hand, everything table is important so the
feature should be always on. Anything else I'm missing here?
> skipTrash option in hive command line
> -------------------------------------
>
> Key: HIVE-6469
> URL: https://issues.apache.org/jira/browse/HIVE-6469
> Project: Hive
> Issue Type: New Feature
> Components: CLI
> Affects Versions: 0.12.0
> Reporter: Jayesh
> Fix For: 0.12.1
>
> Attachments: HIVE-6469.patch
>
>
> hive drop table command deletes the data from HDFS warehouse and puts it into
> Trash.
> Currently there is no way to provide flag to tell warehouse to skip trash
> while deleting table data.
> This ticket is to add skipTrash feature in hive command-line, that looks as
> following.
> hive -e "drop table skipTrash testTable"
> This would be good feature to add, so that user can specify when not to put
> data into trash directory and thus not to fill hdfs space instead of relying
> on trash interval and policy configuration to take care of disk filling issue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
