[
https://issues.apache.org/jira/browse/HBASE-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348766#comment-16348766
]
Abhishek Singh Chouhan commented on HBASE-19858:
------------------------------------------------
While going through the patch realized that we check both
hbase.hstore.block.storage.policy.<family_name> and
hbase.hstore.block.storage.policy for the bulk load case,
hbase.hstore.block.storage.policy.<family_name> gives the impression of setting
the property in general for any cf with the name cf (which is not the case
since in hstore we only check table descriptor or
hbase.hstore.block.storage.policy). Can probably file a Jira to name it
something like hbase.hstore.block.storage.policy.bulkload.cf_name.
> Backport HBASE-14061 (Support CF-level Storage Policy) to branch-1
> ------------------------------------------------------------------
>
> Key: HBASE-19858
> URL: https://issues.apache.org/jira/browse/HBASE-19858
> Project: HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Major
> Fix For: 1.5.0
>
> Attachments: HBASE-19858-branch-1.patch
>
>
> Backport the following commits to branch-1:
> * HBASE-14061 Support CF-level Storage Policy
> * HBASE-14061 Support CF-level Storage Policy (addendum)
> * HBASE-14061 Support CF-level Storage Policy (addendum2)
> * HBASE-15172 Support setting storage policy in bulkload
> * HBASE-17538 HDFS.setStoragePolicy() logs errors on local fs
> * HBASE-18015 Storage class aware block placement for procedure v2 WALs
> * HBASE-18017 Reduce frequency of setStoragePolicy failure warnings
> * HBASE-19016 Coordinate storage policy property name for table schema and
> bulkload
>
> Fix
> * Default storage policy if not configured cannot be "NONE"
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
