[
https://issues.apache.org/jira/browse/HIVE-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041304#comment-14041304
]
Jason Dere commented on HIVE-7090:
----------------------------------
The temp table scratch directory is deleted during session close, and also
marked for deletion upon process close, which should clean up the directory for
normal usage.
If the client dies, this cleanup does not occur and the directory is left in
the user's scratch directory. For HiveServer2, we could try to add cleanup
thread to remove old temp table directories from the scratch directory. For
other users like HiveCLI, there would probably not be any automated cleanup,
similar to other stuff that could get left around in the user's scratch
directory.
> Support session-level temporary tables in Hive
> ----------------------------------------------
>
> Key: HIVE-7090
> URL: https://issues.apache.org/jira/browse/HIVE-7090
> Project: Hive
> Issue Type: Bug
> Components: SQL
> Reporter: Gunther Hagleitner
> Assignee: Harish Butani
> Attachments: HIVE-7090.1.patch, HIVE-7090.2.patch
>
>
> It's common to see sql scripts that create some temporary table as an
> intermediate result, run some additional queries against it and then clean up
> at the end.
> We should support temporary tables properly, meaning automatically manage the
> life cycle and make sure the visibility is restricted to the creating
> connection/session. Without these it's common to see left over tables in
> meta-store or weird errors with clashing tmp table names.
> Proposed syntax:
> CREATE TEMPORARY TABLE ....
> CTAS, CTL, INSERT INTO, should all be supported as usual.
> Knowing that a user wants a temp table can enable us to further optimize
> access to it. E.g.: temp tables should be kept in memory where possible,
> compactions and merging table files aren't required, ...
--
This message was sent by Atlassian JIRA
(v6.2#6252)
