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

Varun Saxena edited comment on YARN-7378 at 10/29/17 9:48 AM:
--------------------------------------------------------------

[~vrushalic], one more comment.
In the documentation, we are referring to version 3.0.0-alpha1. Atleast for the 
jars, this is incorrect.
We can change the file extension from {{md}} to {{md.vm}} and refer to 
{{$\{project.version\}}} instead of specific version inside the documentation. 
Ideally this change should be made for trunk as well.


was (Author: varun_saxena):
[~vrushalic], one more comment.
In the documentation, we are referring to version 3.0.0-alpha1. Atleast for the 
jars, this is incorrect.
We can rename the change the file extension from {{md}} to {{md.vm}} and refer 
to {{$\{project.version\}}} instead of specific version inside the 
documentation. Ideally this change should be made for trunk as well.

> Documentation changes post branch-2 merge
> -----------------------------------------
>
>                 Key: YARN-7378
>                 URL: https://issues.apache.org/jira/browse/YARN-7378
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineclient, timelinereader, timelineserver
>            Reporter: Varun Saxena
>            Assignee: Vrushali C
>         Attachments: YARN-7378-branch-2.0001.patch, 
> YARN-7378-branch-2.0002.patch, YARN-7378-branch-2.0003.patch, schema creation 
> documentation.png
>
>
> Need to update the documentation for the schema creator command. It should 
> include the timeline-service-hbase jar as well as hbase-server jar in 
> classpath when the command is to be run. Due to YARN-7190 classpath changes.



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

---------------------------------------------------------------------
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