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

Rohith Sharma K S commented on YARN-7213:
-----------------------------------------

>From offline mail thread between ATSv2 folks i.e Haibo, Vrushali, Varun, Joep 
>and Vinod, [~haibo.chen] was mentioned that he had tried testing ATSv2 in 
>hadoop-3 with HBase-2-alpha. There are few changes required in order to 
>compile with hbase-2. 

I am copy pasting [~haibo.chen] mail thread content where he has mentioned 
below changes to be made for compiling ATSv2 with HBase-2.
# replace new Tag() with  new ArrayBackedTag()
# replace Tag.asList() with CellUtil.getTags()
# replace Tag.getValue() with Tag.getValueArray()
# replace Tag.fromList() with TagUtil.fromList()
# Add override of void shipped() in FlowScanner
# Replace BaseRegionObserver that FlowRunCoprocessor is extending with 
RegionObserver, since BaseRegionObserver is no longer in HBase 2.0.

[~haibo.chen] would you mind updating a patch which compiles with 
HBase-2-alpha? Probably either you can create new sub task or attach in this 
jira itself! I am fine with either of the ways you choose.

> [Atsv2] Test and validate HBase-2.0.x with Atsv2
> ------------------------------------------------
>
>                 Key: YARN-7213
>                 URL: https://issues.apache.org/jira/browse/YARN-7213
>             Project: Hadoop YARN
>          Issue Type: Task
>            Reporter: Rohith Sharma K S
>            Assignee: Rohith Sharma K S
>
> Hbase-2.0.x officially support hadoop-alpha compilations. And also they are 
> getting ready for Hadoop-beta release so that HBase can release their 
> versions compatible with Hadoop-beta. So, this JIRA is to keep track of 
> HBase-2.0 integration issues. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to