[
https://issues.apache.org/jira/browse/HADOOP-11890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17379845#comment-17379845
]
Brahma Reddy Battula commented on HADOOP-11890:
-----------------------------------------------
[~arp] thanks for your comment.
As [~hemanthboyina] mentioned this is developed on branch-2.7 so there are so
many conflicts with latest trunk.
Internally We resolved against branch-3.1 and deployed the cluster and tested
well ( attached the testcases sheet in HADOOP-17542 )
When we plan for upstream, we feel need to create branch and then go head.
(Somehow this was delayed, [~arp] thanks for pitching here and remind us.)
We are thinking the following approaches to merge to the trunk.
* Create new branch and reopen all the jira's and so that it can run all
patches against the trunk. Or
* Create a single patch against trunk and run jenkins but this will loose
commit history which is might not good .
We thinking go with approach 1 . Let me know your thoughts/suggestions on this..
Hope this should be ok for you.. After your reply, we will create the branch
(jira)
While merging in the discuss thread we keep single patch for review.
> Uber-JIRA: Hadoop should support IPv6
> -------------------------------------
>
> Key: HADOOP-11890
> URL: https://issues.apache.org/jira/browse/HADOOP-11890
> Project: Hadoop Common
> Issue Type: Improvement
> Components: net
> Reporter: Nate Edel
> Assignee: Nate Edel
> Priority: Major
> Labels: ipv6
> Attachments: hadoop_2.7.3_ipv6_commits.txt
>
>
> Hadoop currently treats IPv6 as unsupported. Track related smaller issues to
> support IPv6.
> (Current case here is mainly HBase on HDFS, so any suggestions about other
> test cases/workload are really appreciated.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
