[
https://issues.apache.org/jira/browse/YARN-5071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278587#comment-15278587
]
Sangjin Lee commented on YARN-5071:
-----------------------------------
We have 2 areas of concern:
# running our timeline service server side code under an older environment
(coprocessor, schema creator, and the unit tests)
# running hbase client under the trunk environment
Regarding #1, we have made some effort to isolate at least the unit tests
(YARN-5045), but there is code for coprocessor and the schema creator. We
probably need to isolate them (and its dependencies) so that they are managed
against the old version of hadoop.
While issue #2 might not arise that often (hbase client mostly depends only on
hadoop-common), it is also harder to fix once it happens. Any thoughts on how
we can handle this would be welcome.
> address HBase compatibility issues with trunk
> ---------------------------------------------
>
> Key: YARN-5071
> URL: https://issues.apache.org/jira/browse/YARN-5071
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Critical
>
> The trunk is now adding or planning to add more and more
> backward-incompatible changes. Some examples include
> - remove v.1 metrics classes (HADOOP-12504)
> - update jersey version (HADOOP-9613)
> - target java 8 by default (HADOOP-11858)
> This poses big challenges for the timeline service v.2 as we have a
> dependency on hbase which depends on an older version of hadoop.
> We need to find a way to solve/contain/manage these risks before it is too
> late.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
