[
https://issues.apache.org/jira/browse/HBASE-19858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370296#comment-16370296
]
Sean Busbey commented on HBASE-19858:
-------------------------------------
Our compatibility promises specifically call out "a [minor version] upgrade of
HBase will not require an incompatible upgrade of a dependent project", which I
interpret as including Hadoop. Is Hadoop 2.4 -> 2.7 an incompatible upgrade?
I think we need a DISCUSS thread about dealing with the tail of support for
these Hadoop versions (and perhaps we need to push on them again around what
release lines will be LTS from them).
> 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)
