[
https://issues.apache.org/jira/browse/HIVE-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538224#comment-14538224
]
Alan Gates commented on HIVE-10668:
-----------------------------------
The biggest question here is syntax. I would use STORED IN but STORED AS is
already used for file format and this is orthogonal to file format so it would
be confusing to have grammar STORED AS _fileformat_ STORED IN _storage_tier_
We could use PLACED IN (adding PLACED as a keyword).
We could use STORAGE TIER, though I'm not wild about that as it uses the HDFS
terminology and I don't want to bind this specifically to HDFS.
We could use USING STORAGE. I think this is confusing because it would be
STORED and STORAGE are both keywords.
So for PLACED IN is my favorite, but only because I dislike the others.
Suggestions?
> 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)
