[
https://issues.apache.org/jira/browse/HBASE-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey reopened HBASE-19858:
---------------------------------
reopening because this broke compatibility with Hadoop 2.4 and Hadoop 2.5.
We had a discussion about dropping these versions, but AFAICT the only
consensus was around doing it for HBase 2[1].
The breakage was flagged above in precommit, and has been failing our nightly
checks for branch-1 as well as any subsequent patches targeting branch-1 since.
(the check for Hadoop 2.4 and 2.5 were removed in branch-2 and later branches
in HBASE-18653)
Can we rework the storage policy stuff in a way that's compatible for Hadoop
2.4/2.5 users who don't try to use this feature?
[1]: https://s.apache.org/vW9E
> 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)
