YARN-7378 Documentation changes post branch-2 merge (Vrushali C with Varun Saxena)

hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md → hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md.vm

@@ -236,8 +236,8 @@ is needed for the `flowrun` table creation in the schema creator. The default HD
 For example,
 
     hadoop fs -mkdir /hbase/coprocessor
-    hadoop fs -put hadoop-yarn-server-timelineservice-hbase-3.0.0-alpha1-SNAPSHOT.jar
-           /hbase/coprocessor/hadoop-yarn-server-timelineservice.jar
+    hadoop fs -put hadoop-yarn-server-timelineservice-hbase-${project.version}.jar
+           /hbase/coprocessor/hadoop-yarn-server-timelineservice-hbase-${project.version}.jar
 
 
 If you want to place the jar at a different location on hdfs, there also exists a yarn
@@ -252,9 +252,30 @@ For example,
 ```
 
 ##### <a name="Create_schema"> </a>Step 3) Create the timeline service schema
+The schema creation can be run on the hbase cluster which is going to store the timeline
+service tables. The schema creator tool requires both the timelineservice-hbase as well
+as the hbase-server jars. Hence, during schema creation, you need to ensure that the
+hbase classpath contains the yarn-timelineservice-hbase jar.
+
+On the hbase cluster, you can get it from hdfs since we placed it there for the
+coprocessor in the step above.
+
+```
+   hadoop fs -get  /hbase/coprocessor/hadoop-yarn-server-timelineservice-hbase-${project.version}.jar
+         <local-dir>/.
+```
+
+Next, add it to the hbase classpath as follows:
+
+```
+   export HBASE_CLASSPATH=$HBASE_CLASSPATH:<local-dir>/hadoop-yarn-server-timelineservice-hbase-${project.version}.jar
+```
+
 Finally, run the schema creator tool to create the necessary tables:
 
-    bin/hadoop org.apache.hadoop.yarn.server.timelineservice.storage.TimelineSchemaCreator -create
+```
+    bin/hbase org.apache.hadoop.yarn.server.timelineservice.storage.TimelineSchemaCreator -create
+```
 
 The `TimelineSchemaCreator` tool supports a few options that may come handy especially when you
 are testing. For example, you can use `-skipExistingTable` (`-s` for short) to skip existing tables