[
https://issues.apache.org/jira/browse/HADOOP-14964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260159#comment-16260159
]
Chris Douglas commented on HADOOP-14964:
----------------------------------------
In the future, please raise active backports in the release threads. It would
have been simpler if this issue had been visible _before_ 2.9.0 was released.
Now that 2.9.0 is out, this should target 2.10, which would create 5-7 active
release branches, depending on how pessimistically you want to count them. We
can't sustain that, so let's find a workaround.
How quickly could we spin a 2.9.1 release that includes this feature? If it
could be used in 2.7+ clusters, then users that want to use Aliyun OSS can drop
in the jar. It should work without too many modifications, unless AOSS takes a
dependency that's been upgraded. We probably won't have many 2.9.0 users yet,
so this is the least-bad option we have, IMO. Is anyone willing to RM the
release in the next few weeks?
As discussed on the dev list, we have not released other FS plugins with patch
releases. While initially awkward, it prevents situations where we need to
generate a release in a moribund branch for an active component. Since 2.9 will
likely get regular patch releases for the next few months, it will track with
the AOSS module. It will actually be easier to get users up-to-date versions of
the driver. If it's part of 2.7+, then using an up-to-date version is actually
more complicated, not less.
> AliyunOSS: backport Aliyun OSS module to branch-2 and 2.7+ branches
> -------------------------------------------------------------------
>
> 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
> Attachments: HADOOP-14964-branch-2.000.patch,
> HADOOP-14964-branch-2.8.000.patch, HADOOP-14964-branch-2.8.001.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]