[
https://issues.apache.org/jira/browse/HIVE-7090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14041378#comment-14041378
]
Eugene Koifman commented on HIVE-7090:
--------------------------------------
In that case it may make sense to generate unique names for artifacts that may
be left over. The initial description in this ticket mentions 3rd party tools
that will use this feature - I imagine they will generate the same Temp table
name each time which may cause weird failures after crash.
> 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)
