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

Esteban Gutierrez commented on YARN-6094:
-----------------------------------------

I don't thin thats necessary, our HBase {{hfile.format.version}} has been 
bumped since HBase 0.98 to use HFileV3 by default. However we do still carry 
some tests that programmatically pass that value before stating the HBase 
minicluster.  Some distributions might have opted to ship revert to the old 
HFile version due some compat requirements but as long is documented that the 
Timeline Service needs to use tags and is expected that 
{{hfile.format.version}} is using the default of 3 I don't see any problem. 

> Update the coprocessor to be a dynamically loaded one
> -----------------------------------------------------
>
>                 Key: YARN-6094
>                 URL: https://issues.apache.org/jira/browse/YARN-6094
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Vrushali C
>            Assignee: Vrushali C
>              Labels: yarn-5355-merge-blocker
>         Attachments: YARN-6094.001.patch, YARN-6094-YARN-5355.001.patch, 
> YARN-6094-YARN-5355.002.patch, YARN-6094-YARN-5355.003.patch, 
> YARN-6094-YARN-5355.004.patch
>
>
> The timeline service v2 code base on yarn now uses hbase 1.2.4 after 
> YARN-5976. 
> With this version of hbase, system classes (starting with org.apache.hadoop) 
> can be loaded as table level coprocessors. Hence we should update the 
> timeline service coprocessor to be a dynamically loaded one instead of static 
> loading. 
> This involves code changes as well as documentation updates for deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to