[
https://issues.apache.org/jira/browse/HADOOP-12756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15527773#comment-15527773
]
Anu Engineer commented on HADOOP-12756:
---------------------------------------
[~drankye] I think what Arpit is saying is that he does *not* have an issue
with the code. The proper process to bring in this code would be to call for
vote. Again, it is nothing to do with Aliyun code or technical issues. It gives
the community a chance to review, understand and comment upon the code base
before it is committed. That I think would be the best way to build a community
of contributors around this feature.
If you agree that we should follow the right process, I think we should
*revert* this change and call for a merge vote and merge based on the results
of such a voting thread.
The danger of the precedent what we are doing in this branch would be that
someone else might decide to bring in another feature via this loophole saying
that this was done in Aliyun code merge. That is what I think we want to avoid,
in many senses a rule of law remains a rule only if it is followed
consistently.
I am really sympathetic to what was done and I appreciate the enthusiasm and
the spirit of let us get it done, but I think this list of changes is large
enough for us for us to follow the right process. As far as I can see, few
days spend on voting time will only strengthen the sense of community around
this code base.
[~andrew.wang] Since this is a single commit, reverting and merging will
actuall be a better experience, because it will allow you follow the policy
that was suggested by you
"git merge --no-ff" is also the preferred way of integrating a feature branch
to other branches, e.g. branch-2."
>From
>https://lists.apache.org/thread.html/43cd65c6b6c3c0e8ac2b3c76afd9eff1f78b177fabe9c4a96d9b3d0b@1440189889@%3Ccommon-dev.hadoop.apache.org%3E
> Incorporate Aliyun OSS file system implementation
> -------------------------------------------------
>
> Key: HADOOP-12756
> URL: https://issues.apache.org/jira/browse/HADOOP-12756
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs
> Affects Versions: HADOOP-12756
> Reporter: shimingfei
> Assignee: shimingfei
> Fix For: HADOOP-12756
>
> Attachments: Aliyun-OSS-integration-v2.pdf,
> Aliyun-OSS-integration.pdf, HADOOP-12756-v02.patch, HADOOP-12756.003.patch,
> HADOOP-12756.004.patch, HADOOP-12756.005.patch, HADOOP-12756.006.patch,
> HADOOP-12756.007.patch, HADOOP-12756.008.patch, HADOOP-12756.009.patch,
> HADOOP-12756.010.patch, HCFS User manual.md, OSS integration.pdf
>
>
> Aliyun OSS is widely used among China’s cloud users, but currently it is not
> easy to access data laid on OSS storage from user’s Hadoop/Spark application,
> because of no original support for OSS in Hadoop.
> This work aims to integrate Aliyun OSS with Hadoop. By simple configuration,
> Spark/Hadoop applications can read/write data from OSS without any code
> change. Narrowing the gap between user’s APP and data storage, like what have
> been done for S3 in Hadoop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
