hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-10668) Allow users to specify storage tiers for a table
Date Mon, 11 May 2015 20:46:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538620#comment-14538620
] 

Alan Gates commented on HIVE-10668:
-----------------------------------

I like PERSISTED IN better than PLACED IN.

bq. Of a different note, I assume that a table can be "altered" so as to change the storage
tier after creation.
Yes, see original description.

I envision two DDL changes:
CREATE TABLE ... PERSISTED IN _tier_ 
ALTER TABLE ... SET PERSISTED IN _tier_

> Allow users to specify storage tiers for a table
> ------------------------------------------------
>
>                 Key: HIVE-10668
>                 URL: https://issues.apache.org/jira/browse/HIVE-10668
>             Project: Hive
>          Issue Type: New Feature
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>
> Starting with Hadoop 2.6, HDFS files can be assigned to storage tiers.  Current supported
options include SSD and single copy in memory.
> It is already possible to default all temp tables to a given tier (HIVE-7313).  
> It should be possible to specify for a given table, temp table, or when they are added,
materialized views (HIVE-10459).  It should also be possible to change the storage tier for
a given table or view.
> This should be done in a way that it is not tied explicitly to HDFS (ie, other systems
may have alternate storage tiers or related concepts).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message