hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SammiChen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14964) AliyunOSS: backport Aliyun OSS module to branch-2
Date Wed, 29 Nov 2017 08:45:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16270412#comment-16270412

SammiChen commented on HADOOP-14964:

Hi [~chris.douglas], thanks for summarize the discussion here. 

bq. Please cherry-pick from branch-2.9 to branch-2.8, then from branch-2.8 to branch-2.8.3
so the lineage is clear.

Got it. 

bq. For (1), what are all the transitive dependencies for this module? 

 aliyun-sdk-oss  2.8.1 is used in trunk, branch-2 and branch-2.9.  It has three external dependencies,
net.sf.json-lib/json-lib(not used in Hadoop), org.apache.httpcomponents/httpclient and org.jdom/jdom(same
1.1 version as Hadoop). For httpclient, Hadoop use 4.5.2, oss sdk use 4.4.1. 4.5.2 fully support
the function oss sdk used in 4.4.1. So it's OK for oss-sdk to use the current 4.5.2 httpclient
in Hadoop, also httpclient dependency exclusion is declared for oss-sdk in trunk and branch-2.9
to avoid any conflict.  I would say basically the oss sdk transitive dependencies is not a

bq.  For (2), if we take the current branch-2.9 and cut a 2.9.1 release, that would tranquilize
anxiety about the upgrade path. SammiChen, would you be able to RM this? Arun Suresh and Subru
Krishnan may be able to help by providing pointers to release docs.

Thanks for the asking. I would like to take the RM role if possible. Also guide is strongly

bq. As policy, (4) is stickier. Even releasing this with 2.9.1 doesn't strictly adhere to
our rules, but it's better than adding another, active release branch. The case for 2.8.3
is more problematic. The cadence for 2.8.x will decelerate more rapidly than 2.9.x, so fixes
to Aliyun OSS will be released less often. We may not do its users a favor by including an
outdated client with their 2.8 clusters. Frankly, maintenance is also simpler when we disallow
feature backports into patch releases, rather than discussing the merits of each one. This
can't become a precedent; it takes too much time.

I do understand the concerns. Previously we don't know the release process very well,  should
proposal the request earlier. We will convey community's feedback to Aliyun OSS team and discuss
the possible solutions.


> AliyunOSS: backport Aliyun OSS module to branch-2
> -------------------------------------------------
>                 Key: HADOOP-14964
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14964
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/oss
>            Reporter: Genmao Yu
>            Assignee: SammiChen
>             Fix For: 2.9.1
>         Attachments: HADOOP-14964-branch-2.000.patch, HADOOP-14964-branch-2.8.000.patch,
HADOOP-14964-branch-2.8.001.patch, HADOOP-14964-branch-2.9.001.patch

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message