hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19203) Update Hadoop version used for build to 2.7.4
Date Tue, 07 Nov 2017 21:53:00 GMT

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

Andrew Purtell commented on HBASE-19203:
----------------------------------------

bq. Dropping 2.7 sounds super ill-advised given the length of time 2.8.2 has been out, but
Hadoop gonna Hadoop I guess. Not sure if it's worth reviving our discuss thread about requesting
maintenance releases from our dependencies.

To be precise, I have not seen discussion about dropping 2.7. What I have seen is discussion
about maintaining 2.8 and 2.9 (and possibly a 2.10), and 3.0, and maybe a 3.1, with no mention
of 2.7 or earlier. I would imagine 2.8 is where the line will be drawn, but we can always
request 2.7 maintenance releases. 

> Update Hadoop version used for build to 2.7.4
> ---------------------------------------------
>
>                 Key: HBASE-19203
>                 URL: https://issues.apache.org/jira/browse/HBASE-19203
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 1.4.0, 1.5.0
>
>         Attachments: HBASE-19203-branch-1.patch, HBASE-19203-branch-1.patch, HBASE-19203.patch
>
>
> See parent. 
> 2.5 is really old. 
> Based on discussions I've seen on the Hadoop *-dev@ lists, Hadoop is even about to drop
2.7. Using 2.7 for convenience binary builds is fine. We should probably update it to 2.8.2,
but that's not strictly necessary so I'll opt for the oldest. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message