carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chenliang...@apache.org
Subject [10/13] incubator-carbondata-site git commit: Updated website for CarbonData V 1.0
Date Thu, 19 Jan 2017 23:15:00 GMT
http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/configuring.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/configuring.html b/src/main/webapp/docs/latest/configuring.html
deleted file mode 100644
index 51c0e6c..0000000
--- a/src/main/webapp/docs/latest/configuring.html
+++ /dev/null
@@ -1,478 +0,0 @@
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style>
-
-</style></head><body id="preview">
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-“License”); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-&quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-<h1><a id="Configuring_CarbonData_20"></a>Configuring CarbonData</h1>
-<p>This tutorial guides you through the advanced configurations of CarbonData :</p>
-<ul>
-<li><a href="#system-configuration">System Configuration</a></li>
-<li><a href="#performance-configuration">Performance Configuration</a></li>
-<li><a href="#miscellaneous-configuration">Miscellaneous Configuration</a></li>
-<li><a href="#spark-configuration">Spark Configuration</a></li>
-</ul>
-<div id="system-configuration">
-</div>
-<h2><a id="System_Configuration_29"></a>System Configuration</h2>
-<p>This section provides the details of all the configurations required for the CarbonData System.<br>
-<center>
-<i>System Configuration in carbon.properties</i>
-</center><br />
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Property</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.storelocation</td>
-<td>/user/hive/warehouse/carbon.store</td>
-<td>Location where CarbonData will create the store, and write the data in its own format. NOTE: Store location should be in HDFS.</td>
-</tr>
-<tr>
-<td>carbon.ddl.base.hdfs.url</td>
-<td>hdfs://hacluster/opt/data</td>
-<td>This property is used to configure the HDFS relative path from the HDFS base path, configured in fs.defaultFS. The path configured in carbon.ddl.base.hdfs.url will be appended to the HDFS path configured in fs.defaultFS. If this path is configured, then user need not pass the complete path while dataload. For example: If absolute path of the csv file is hdfs://10.18.101.155:54310/data/cnbc/2016/xyz.csv, the path “hdfs://10.18.101.155:54310” will come from property fs.defaultFS and user can configure the /data/cnbc/ as carbon.ddl.base.hdfs.url. Now while dataload user can specify the csv path as /2016/xyz.csv.</td>
-</tr>
-<tr>
-<td>carbon.badRecords.location</td>
-<td>/opt/Carbon/Spark/badrecords</td>
-<td>Path where the bad records are stored.</td>
-</tr>
-<tr>
-<td>carbon.kettle.home</td>
-<td>$SPARK_HOME/carbonlib/carbonplugins</td>
-<td>Path used by CarbonData internally to create graph for loading the data.</td>
-</tr>
-<tr>
-<td>carbon.data.file.version</td>
-<td>2</td>
-<td>If this parameter value is set to 1, then CarbonData will support the data load which is in old format. If the value is set to 2, then CarbonData will support the data load of new format only. NOTE: The file format created before DataSight Spark V100R002C30 is considered as old format.</td>
-</tr>
-</tbody>
-</table>
-<div id="performance-configuration"></div>
-<h2><a id="Performance_Configuration_41"></a>Performance Configuration</h2>
-<p>This section provides the details of all the configurations required for CarbonData Performance Optimization.<br>
-<center>
-  <i>Performance Configuration in carbon.properties</i>
-</center></p>
-<ol>
-<li><strong>Data Loading Configuration</strong>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-<th>Range</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.sort.file.buffer.size</td>
-<td>20</td>
-<td>File read buffer size used during sorting. This value is expressed in MB.</td>
-<td>Min=1 and Max=100</td>
-</tr>
-<tr>
-<td>carbon.graph.rowset.size</td>
-<td>100000</td>
-<td>Rowset size exchanged between data load graph steps.</td>
-<td>Min=500 and Max=1000000</td>
-</tr>
-<tr>
-<td>carbon.number.of.cores.while.loading</td>
-<td>6</td>
-<td>Number of cores to be used while loading data.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.sort.size</td>
-<td>500000</td>
-<td>Record count to sort and write intermediate files to temp.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.enableXXHash</td>
-<td>true</td>
-<td>Algorithm for hashmap for hashkey calculation.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.number.of.cores.block.sort</td>
-<td>7</td>
-<td>Number of cores to use for block sort while loading data.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.max.driver.lru.cache.size</td>
-<td>-1</td>
-<td>Max LRU cache size upto which data will be loaded at the driver side. This value is expressed in MB. Default value of -1 means there is no memory limit for caching. Only integer values greater than 0 are accepted.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.max.executor.lru.cache.size</td>
-<td>-1</td>
-<td>Max LRU cache size upto which data will be loaded at the executor side. This value is expressed in MB. Default value of -1 means there is no memory limit for caching. Only integer values greater than 0 are accepted. If this parameter is not configured, then the carbon.max.driver.lru.cache.size value will be considered. </td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.merge.sort.prefetch</td>
-<td>true</td>
-<td>Enable prefetch of data during merge sort while reading data from sort temp files in data loading.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.update.persist.enable</td>
-<td>true</td>
-<td>Enabling this parameter considers persistent data. Enabling this will reduce the execution time of UPDATE operation.</td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</li>
-
-<li><strong>Compaction Configuration</strong>
-
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-<th>Range</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.number.of.cores.while.compacting</td>
-<td>2</td>
-<td>Number of cores which are used to write data during compaction.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.compaction.level.threshold</td>
-<td>4, 3</td>
-<td>This property is for minor compaction which decides how many segments to be merged. Example: If it is set as 2, 3 then minor compaction will be triggered for every 2 segments. 3 is the number of level 1 compacted segment which is further compacted to new segment.</td>
-<td>Valid values are from 0-100.</td>
-</tr>
-<tr>
-<td>carbon.major.compaction.size</td>
-<td>1024</td>
-<td>Major compaction size can be configured using this parameter. Sum of the segments which is below this threshold will be merged. This value is expressed in MB.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.horizontal.compaction.enable</td>
-<td>true</td>
-<td>This property is used to turn ON/OFF horizontal compaction. After every DELETE and UPDATE statement, horizontal compaction may occur in case the delta (DELETE/ UPDATE) files becomes more than specified threshold.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.horizontal.UPDATE.compaction.threshold</td>
-<td>1</td>
-<td>This property specifies the threshold limit on number of UPDATE delta files within a segment. In case the number of delta files goes beyond the threshold, the UPDATE delta files within the segment becomes eligible for horizontal compaction and compacted into single UPDATE delta file.</td>
-<td>Values between 1 to 10000.</td>
-</tr>
-<tr>
-<td>carbon.horizontal.DELETE.compaction.threshold</td>
-<td>1</td>
-<td>This property specifies the threshold limit on number of DELETE delta files within a block of a segment. In case the number of delta files goes beyond the threshold, the DELETE delta files for the particular block of the segment becomes eligible for horizontal compaction and compacted into single DELETE delta file.</td>
-<td>Values between 1 to 10000.</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li><strong>Query Configuration</strong>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-<th>Range</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.number.of.cores</td>
-<td>4</td>
-<td>Number of cores to be used while querying.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.inmemory.record.size</td>
-<td>120000</td>
-<td>Number of records to be in memory while querying.</td>
-<td>Min=100000 and Max=240000</td>
-</tr>
-<tr>
-<td>carbon.enable.quick.filter</td>
-<td>false</td>
-<td>Improves the performance of filter query.</td>
-<td></td>
-</tr>
-<tr>
-<td>no.of.cores.to.load.blocks.in.driver</td>
-<td>10</td>
-<td>Number of core to load the blocks in driver.</td>
-<td></td>
-</tr>
-</tbody>
-</table>
-</li>
-</ol>
-<div id="miscellaneous-configuration"></div>
-<h2><a id="Miscellaneous_Configuration_81"></a>Miscellaneous Configuration</h2>
-<center>
-  <i>Extra Configuration in carbon.properties</i>
-</center>
-</p>
-<ol>
-<li><strong>Time format for CarbonData</strong>
-
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Format</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.timestamp.format</td>
-<td>yyyy-MM-dd HH:mm:ss</td>
-<td>Timestamp format of input data used for timestamp data type.</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li><strong>Dataload Configuration</strong>
-
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.sort.file.write.buffer.size</td>
-<td>10485760</td>
-<td>File write buffer size used during sorting.</td>
-</tr>
-<tr>
-<td>carbon.lock.type</td>
-<td>LOCALLOCK</td>
-<td>This configuration specifies the type of lock to be acquired during concurrent operations on table. There are following types of lock implementation: - LOCALLOCK: Lock is created on local file system as file. This lock is useful when only one spark driver (thrift server) runs on a machine and no other CarbonData spark application is launched concurrently. - HDFSLOCK: Lock is created on HDFS file system as file. This lock is useful when multiple CarbonData spark applications are launched and no ZooKeeper is running on cluster and HDFS supports file based locking.</td>
-</tr>
-<tr>
-<td>carbon.sort.intermediate.files.limit</td>
-<td>20</td>
-<td>Minimum number of intermediate files after which merged sort can started.</td>
-</tr>
-<tr>
-<td>carbon.block.meta.size.reserved.percentage</td>
-<td>10</td>
-<td>Space reserved in percentage for writing block meta data in CarbonData file.</td>
-</tr>
-<tr>
-<td>carbon.csv.read.buffersize.byte</td>
-<td>1048576</td>
-<td>csv reading buffer size.</td>
-</tr>
-<tr>
-<td>high.cardinality.value</td>
-<td>100000</td>
-<td>To identify and apply compression for non-high cardinality columns.</td>
-</tr>
-<tr>
-<td>carbon.merge.sort.reader.thread</td>
-<td>3</td>
-<td>Maximum no of threads used for reading intermediate files for final merging.</td>
-</tr>
-<tr>
-<td>carbon.load.metadata.lock.retries</td>
-<td>3</td>
-<td>Maximum number of retries to get the metadata lock for loading data to table.</td>
-</tr>
-<tr>
-<td>carbon.load.metadata.lock.retry.timeout.sec</td>
-<td>5</td>
-<td>Interval between the retries to get the lock.</td>
-</tr>
-<tr>
-<td>carbon.tempstore.location</td>
-<td>/opt/Carbon/TempStoreLoc</td>
-<td>Temporary store location. By default it takes System.getProperty(“java.io.tmpdir”).</td>
-</tr>
-<tr>
-<td>carbon.load.log.counter</td>
-<td>500000</td>
-<td>Data loading records count logger.</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li><strong>Compaction Configuration</strong>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.numberof.preserve.segments</td>
-<td>0</td>
-<td>If the user wants to preserve some number of segments from being compacted then he can set this property. Example: carbon.numberof.preserve.segments=2 then 2 latest segments will always be excluded from the compaction. No segments will be preserved by default.</td>
-</tr>
-<tr>
-<td>carbon.allowed.compaction.days</td>
-<td>0</td>
-<td>Compaction will merge the segments which are loaded with in the specific number of days configured. Example: If the configuration is 2, then the segments which are loaded in the time frame of 2 days only will get merged. Segments which are loaded 2 days apart will not be merged. This is disabled by default.</td>
-</tr>
-<tr>
-<td>carbon.enable.auto.load.merge</td>
-<td>false</td>
-<td>To enable compaction while data loading.</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li><strong>Query Configuration</strong>
-
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>max.query.execution.time</td>
-<td>60</td>
-<td>Maximum time allowed for one query to be executed. The value is in minutes.</td>
-</tr>
-<tr>
-<td>carbon.enableMinMax</td>
-<td>true</td>
-<td>Min max is feature added to enhance query performance. To disable this feature, set it false.</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li><strong>Global Dictionary Configurations</strong>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>high.cardinality.identify.enable</td>
-<td>true</td>
-<td>If the parameter is true, the high cardinality columns of the dictionary code are automatically recognized and these columns will not be used as global dictionary encoding. If the parameter is false, all dictionary encoding columns are used as dictionary encoding. The high cardinality column must meet the following requirements: value of cardinality &gt; configured value of high.cardinalityEqually, the value of cardinality is higher than the threshold.value of cardinality/ row number x 100 &gt; configured value of high.cardinality.row.count.percentageEqually, the ratio of the cardinality value to data row number is higher than the configured percentage.</td>
-</tr>
-<tr>
-<td>high.cardinality.threshold</td>
-<td>1000000</td>
-<td>Threshold to identify whether high cardinality column. Configuration value formula: Value of cardinality &gt; configured value of high.cardinality. The minimum value is 10000.</td>
-</tr>
-<tr>
-<td>high.cardinality.row.count.percentage</td>
-<td>80</td>
-<td>Percentage to identify whether column cardinality is more than configured percent of total row count. Configuration value formula: Value of cardinality/ row number x 100 &gt; configured value of high.cardinality.row.count.percentage. The value of the parameter must be larger than 0.</td>
-</tr>
-<tr>
-<td>carbon.cutOffTimestamp</td>
-<td>1970-01-01 05:30:00</td>
-<td>Sets the start date for calculating the timestamp. Java counts the number of milliseconds from start of “1970-01-01 00:00:00”. This property is used to customize the start of position. For example “2000-01-01 00:00:00”. The date must be in the form “carbon.timestamp.format”. NOTE: CarbonData supports data store up to 68 years from the cut-off time defined. For example, if the cut-off time is 1970-01-01 05:30:00, then the data can be stored up to 2038-01-01 05:30:00.</td>
-</tr>
-<tr>
-<td>carbon.timegranularity</td>
-<td>SECOND</td>
-<td>The property used to set the data granularity level DAY, HOUR, MINUTE, or SECOND.</td>
-</tr>
-</tbody>
-</table>
-</li>
-</ol>
-<div id="spark-configuration">
-</div>
-<h2><a id="Spark_Configuration_133"></a>Spark Configuration</h2>
-<center>
-  <i>Spark Configuration Reference in spark-defaults.conf</i>
-</center>
-</p>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default Value</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>spark.driver.memory</td>
-<td>1g</td>
-<td>Amount of memory to use for the driver process, i.e. where SparkContext is initialized. NOTE: In client mode, this config must not be set through the SparkConf directly in your application because the driver JVM has already started at that point. Instead, please set this through the --driver-memory command line option or in your default properties file.</td>
-</tr>
-<tr>
-<td>spark.executor.memory</td>
-<td>1g</td>
-<td>Amount of memory to use per executor process.</td>
-</tr>
-<tr>
-<td>spark.sql.bigdata.register.analyseRule</td>
-<td>org.apache.spark.sql.hive.acl.CarbonAccessControlRules</td>
-<td>CarbonAccessControlRules need to be set for enabling Access Control.</td>
-</tr>
-</tbody>
-</table>
-
-<script type="text/javascript">
- $('a[href*="#"]:not([href="#"])').click(function() {
-   if (location.pathname.replace(/^\//, '') == this.pathname.replace(/^\//, '') && location.hostname == this.hostname) {
-    var target = $(this.hash);
-    target = target.length ? target : $('[name=' + this.hash.slice(1) + ']');
-    if (target.length) 
-        { $('html, body').animate({    scrollTop: target.offset().top - 52 },100);
-          return false;
-        }
-     }
-  });
-</script>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/data-management.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/data-management.html b/src/main/webapp/docs/latest/data-management.html
new file mode 100644
index 0000000..b756271
--- /dev/null
+++ b/src/main/webapp/docs/latest/data-management.html
@@ -0,0 +1,175 @@
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+--><h1>Data Management</h1><p>This tutorial is going to introduce you to the conceptual details of data management like:</p>
+<ul>
+  <li><a href="#loading-data">Loading Data</a></li>
+  <li><a href="#deleting-data">Deleting Data</a></li>
+  <li><a href="#compacting-data">Compacting Data</a></li>
+  <li><a href="#updating-data">Updating Data</a></li>
+</ul><h2>Loading Data</h2>
+<ul>
+  <li><strong>Scenario</strong></li>
+</ul><p>After creating a table, you can load data to the table using the <a href="dml-operation-on-carbondata.html">LOAD DATA</a> command. The loaded data is available for querying.  When data load is triggered, the data is encoded in CarbonData format and copied into HDFS CarbonData store path (specified in carbon.properties file)  in compressed, multi dimensional columnar format for quick analysis queries. The same command can be used to load new data or to  update the existing data. Only one data load can be triggered for one table. The high cardinality columns of the dictionary encoding are  automatically recognized and these columns will not be used for dictionary encoding.</p>
+<ul>
+  <li><strong>Procedure</strong></li>
+</ul><p>Data loading is a process that involves execution of multiple steps to read, sort and encode the data in CarbonData store format.  Each step is executed on different threads. After data loading process is complete, the status (success/partial success) is updated to  CarbonData store metadata. The table below lists the possible load status.</p>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Status </th>
+      <th>Description </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>Success </td>
+      <td>All the data is loaded into table and no bad records found. </td>
+    </tr>
+    <tr>
+      <td>Partial Success </td>
+      <td>Data is loaded into table and bad records are found. Bad records are stored at carbon.badrecords.location. </td>
+    </tr>
+  </tbody>
+</table><p>In case of failure, the error will be logged in error log. Details of loads can be seen with <a href="dml-operation-on-carbondata.html">SHOW SEGMENTS</a> command. The show segment command output consists of :</p>
+<ul>
+  <li>SegmentSequenceID</li>
+  <li>START_TIME OF LOAD</li>
+  <li>END_TIME OF LOAD</li>
+  <li>LOAD STATUS</li>
+</ul><p>The latest load will be displayed first in the output.</p><p>Refer to <a href="dml-operation-on-carbondata.html">DML operations on CarbonData</a> for load commands.</p><h2>Deleting Data</h2>
+<ul>
+  <li><strong>Scenario</strong></li>
+</ul><p>If you have loaded wrong data into the table, or too many bad records are present and you want to modify and reload the data, you can delete required data loads.  The load can be deleted using the Segment Sequence Id or if the table contains date field then the data can be deleted using the date field.  If there are some specific records that need to be deleted based on some filter condition(s) we can delete by records.</p>
+<ul>
+  <li><strong>Procedure</strong></li>
+</ul><p>The loaded data can be deleted in the following ways:</p>
+<ul>
+  <li><p>Delete by Segment ID</p><p>After you get the segment ID of the segment that you want to delete, execute the <a href="dml-operation-on-carbondata.html">DELETE</a> command for the selected segment.  The status of deleted segment is updated to Marked for delete / Marked for Update.</p></li>
+</ul>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>SegmentSequenceId </th>
+      <th>Status </th>
+      <th>Load Start Time </th>
+      <th>Load End Time </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>0 </td>
+      <td>Success </td>
+      <td>2015-11-19 19:14:... </td>
+      <td>2015-11-19 19:14:... </td>
+    </tr>
+    <tr>
+      <td>1 </td>
+      <td>Marked for Update </td>
+      <td>2015-11-19 19:54:... </td>
+      <td>2015-11-19 20:08:... </td>
+    </tr>
+    <tr>
+      <td>2 </td>
+      <td>Marked for Delete </td>
+      <td>2015-11-19 20:25:... </td>
+      <td>2015-11-19 20:49:... </td>
+    </tr>
+  </tbody>
+</table>
+<ul>
+  <li><p>Delete by Date Field</p><p>If the table contains date field, you can delete the data based on a specific date.</p></li>
+  <li><p>Delete by Record</p><p>To delete records from CarbonData table based on some filter Condition(s).</p><p>For delete commands refer to <a href="dml-operation-on-carbondata.html">DML operations on CarbonData</a>.</p></li>
+  <li><p><strong>NOTE</strong>:</p>
+  <ul>
+    <li>When the delete segment DML is called, segment will not be deleted physically from the file system. Instead the segment status will be marked as "Marked for Delete". For the query execution, this deleted segment will be excluded.</li>
+  </ul>
+  <ul>
+    <li>The deleted segment will be deleted physically during the next load operation and only after the maximum query execution time configured using "max.query.execution.time". By default it is 60 minutes.</li>
+  </ul>
+  <ul>
+    <li>If the user wants to force delete the segment physically then he can use CLEAN FILES Command.</li>
+  </ul></li>
+</ul><p>Example :</p><p><code>
+CLEAN FILES FOR TABLE table1
+</code></p><p>This DML will physically delete the segment which are "Marked for delete" immediately.</p><h2>Compacting Data</h2>
+<ul>
+  <li><strong>Scenario</strong></li>
+</ul><p>Frequent data ingestion results in several fragmented CarbonData files in the store directory. Since data is sorted only within each load, the indices perform only within each  load. This means that there will be one index for each load and as number of data load increases, the number of indices also increases. As each index works only on one load,  the performance of indices is reduced. CarbonData provides provision for compacting the loads. Compaction process combines several segments into one large segment by merge sorting the data from across the segments. </p>
+<ul>
+  <li><strong>Procedure</strong></li>
+</ul><p>There are two types of compaction Minor and Major compaction.</p>
+<ul>
+  <li><p><strong>Minor Compaction</strong></p><p>In minor compaction the user can specify how many loads to be merged. Minor compaction triggers for every data load if the parameter carbon.enable.auto.load.merge is set. If any segments are available to be merged, then compaction will  run parallel with data load. There are 2 levels in minor compaction.</p>
+  <ul>
+    <li>Level 1: Merging of the segments which are not yet compacted.</li>
+    <li>Level 2: Merging of the compacted segments again to form a bigger segment.</li>
+  </ul></li>
+  <li><p><strong>Major Compaction</strong></p><p>In Major compaction, many segments can be merged into one big segment. User will specify the compaction size until which segments can be merged. Major compaction is usually done during the off-peak time. </p></li>
+</ul><p>There are number of parameters related to Compaction that can be set in carbon.properties file </p>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Default </th>
+      <th>Application </th>
+      <th>Description </th>
+      <th>Valid Values </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>carbon.compaction.level.threshold </td>
+      <td>4, 3 </td>
+      <td>Minor </td>
+      <td>This property is for minor compaction which decides how many segments to be merged. Example: If it is set as 2, 3 then minor compaction will be triggered for every 2 segments. 3 is the number of level 1 compacted segment which is further compacted to new segment. </td>
+      <td>NA </td>
+    </tr>
+    <tr>
+      <td>carbon.major.compaction.size </td>
+      <td>1024 MB </td>
+      <td>Major </td>
+      <td>Major compaction size can be configured using this parameter. Sum of the segments which is below this threshold will be merged. </td>
+      <td>NA </td>
+    </tr>
+    <tr>
+      <td>carbon.numberof.preserve.segments </td>
+      <td>0 </td>
+      <td>Minor/Major </td>
+      <td>If the user wants to preserve some number of segments from being compacted then he can set this property. Example: carbon.numberof.preserve.segments=2 then 2 latest segments will always be excluded from the compaction. No segments will be preserved by default. </td>
+      <td>0-100 </td>
+    </tr>
+    <tr>
+      <td>carbon.allowed.compaction.days </td>
+      <td>0 </td>
+      <td>Minor/Major </td>
+      <td>Compaction will merge the segments which are loaded within the specific number of days configured. Example: If the configuration is 2, then the segments which are loaded in the time frame of 2 days only will get merged. Segments which are loaded 2 days apart will not be merged. This is disabled by default. </td>
+      <td>0-100 </td>
+    </tr>
+    <tr>
+      <td>carbon.number.of.cores.while.compacting </td>
+      <td>2 </td>
+      <td>Minor/Major </td>
+      <td>Number of cores which is used to write data during compaction. </td>
+      <td>0-100 </td>
+    </tr>
+  </tbody>
+</table><p>For compaction commands refer to <a href="ddl-operation-on-carbondata.html">DDL operations on CarbonData</a></p><h2>Updating Data</h2>
+<ul>
+  <li><p><strong>Scenario</strong></p><p>Sometimes after the data has been ingested into the System, it is required to be updated. Also there may be situations where some specific columns need to be updated on the basis of column expression and optional filter conditions.</p></li>
+  <li><p><strong>Procedure</strong></p><p>To update we need to specify the column expression with an optional filter condition(s).</p><p>For update commands refer to <a href="dml-operation-on-carbondata.html">DML operations on CarbonData</a>.</p></li>
+</ul>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/data_management.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/data_management.html b/src/main/webapp/docs/latest/data_management.html
deleted file mode 100644
index 2dd6439..0000000
--- a/src/main/webapp/docs/latest/data_management.html
+++ /dev/null
@@ -1,231 +0,0 @@
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style>
-
-</style></head><body id="preview">
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-“License”); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-&quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-<h1><a id="Data_Management_18"></a>Data Management</h1>
-<p>This tutorial is going to introduce you to the conceptual details of data management like :</p>
-<ul>
-<li><a href="#loading-data">Loading Data</a></li>
-<li><a href="#deleting-data">Deleting Data</a></li>
-<li><a href="#compacting-data">Compacting data</a></li>
-</ul>
-<div id="loading-data"></div>
-<h2><a id="Loading_Data_25"></a>Loading Data</h2>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>
-
-After creating a table, you can load data to the table using the <a href="dml.html#load-data">LOAD DATA</a> command. The loaded data is available for querying. When data load is triggered, the data is encoded in CarbonData format and copied into HDFS CarbonData store path(specified in carbon.properties file) in compressed, multi dimensional columnar format for quick analysis queries. The same command can be used to load new data or to update the existing data. Only one data load can be triggered for one table. The high cardinality columns of the dictionary encoding are automatically recognized and these columns will not be used for dictionary encoding.</p>
-</li>
-<li>
-<p><strong>Procedure</strong></p>
-<p>Data loading is a process that involves execution of multiple steps to read, sort and encode the data in CarbonData store format. Each step is executed on different threads. After data loading process is complete, the status (success/partial success) is updated to CarbonData store metadata. The table below lists the possible load status.</p>
-</li>
-</ul>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Status</th>
-<th>Description</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>Success</td>
-<td>All the data is loaded into table and no bad records found.</td>
-</tr>
-<tr>
-<td>Partial Success</td>
-<td>Data is loaded into table and bad records are found. Bad records are stored at carbon.badrecords.location.</td>
-</tr>
-</tbody>
-</table>
-<p>In case of failure, the error will be logged in error log. Details of loads can be seen with <a href="dml.html#show-segments">SHOW SEGMENTS</a> command. The show segment command output consists of :</p>
-<ul>
-<li>SegmentSequenceID</li>
-<li>START_TIME OF LOAD</li>
-<li>END_TIME OF LOAD</li>
-<li>LOAD STATUS</li>
-</ul>
-<p>The latest load will be displayed first in the output.</p>
-<p>Refer to <a href="dml.html">DML operations on CarbonData</a> for load commands.</p>
-<div id ="deleting-data"></div>
-<h2>Deleting Data</h2>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>If you have loaded wrong data into the table, or too many bad records are present and you want to modify and reload the data, you can delete required data loads. The load can be deleted using the Segment Sequence Id or if the table contains date field then the data can be deleted using the date field.</p>
-</li>
-<li>
-<p><strong>Procedure</strong></p>
-<p>The loaded data can be deleted in the following ways :</p>
-<ol>
-<li>
-<p>Delete by Segment ID</p>
-<p>After you get the segment ID of the segment that you want to delete, execute the <a href="dml.html#delete-segment-by-id">DELETE</a> command for the selected segment. The status of deleted segment is updated to Marked for delete / Marked for Update.</p>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>SegmentSequenceId</th>
-<th>Status</th>
-<th>Load Start Time</th>
-<th>Load End Time</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>0</td>
-<td>Success</td>
-<td>2015-11-19 19:14:…</td>
-<td>2015-11-19 19:14:…</td>
-</tr>
-<tr>
-<td>1</td>
-<td>Marked for Update</td>
-<td>2015-11-19 19:54:…</td>
-<td>2015-11-19 20:08:…</td>
-</tr>
-<tr>
-<td>2</td>
-<td>Marked for Delete</td>
-<td>2015-11-19 20:25:…</td>
-<td>2015-11-19 20:49:…</td>
-</tr>
-</tbody>
-</table>
-</li>
-<li>
-<p>Delete by Date Field</p>
-<p>If the table contains date field, you can delete the data based on a specific date.</p>
-<p>For delete commands refer to <a href="dml.html">DML operations on CarbonData</a>.</p>
-</li>
-</ol>
-<p>NOTE:</p>
-<ul>
-<li>
-<p>When the delete segment DML is called, segment will not be deleted physically from the file system. Instead the segment status will be marked as “Marked for Delete”. For the query execution, this deleted segment will be excluded.</p>
-</li>
-<li>
-<p>The deleted segment will be deleted physically during the next load operation and only after the maximum query execution time configured using “max.query.execution.time”. By default it is 60 minutes.</p>
-</li>
-<li>
-<p>If the user wants to force delete the segment physically then he can use CLEAN FILES</a> command.
-Example:
-<pre><code>
-CLEAN FILES FOR TABLE table1
-</code>
-</pre>
- This DML will physically delete the segment which are “Marked for delete” immediately.</p>
-</li>
-</ul>
-</li>
-</ul>
-<div id="compacting-data"></div>
-<h2>Compacting Data</h2>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>Frequent data ingestion results in several fragmented carbonData files in the store directory. Since data is sorted only within each load, the indices perform only within each load. This mean that there will be one index for each load and as number of data load increases, the number of indices also increases. As each index works only on one load, the performance of indices is reduced. CarbonData provides provision for compacting the loads. Compaction process combines several segments into one large segment by merge sorting the data from across the segments.</p>
-</li>
-<li>
-<p><strong>Procedure</strong></p>
-<p>There are two types of compaction Minor and Major compaction.</p>
-<ul>
-<li>
-<p><strong>Minor Compaction</strong></p>
-<p>In minor compaction the user can specify how many loads to be merged. Minor compaction triggers for every data load if the parameter carbon.enable.auto.load.merge is set. If any segments are available to be merged, then compaction will 
-run parallel with data load. There are 2 levels in minor compaction.</p>
-<ul>
-<li>Level 1: Merging of the segments which are not yet compacted.</li>
-<li>Level 2: Merging of the compacted segments again to form a bigger segment.</li>
-</ul>
-</li>
-<li>
-<p><strong>Major Compaction</strong></p>
-<p>In Major compaction, many segments can be merged into one big segment. User will specify the compaction size until which segments can be merged. Major compaction is usually done during the off-peak time.</p>
-</li>
-</ul>
-<p>There are number of parameters related to Compaction that can be set in carbon.properties file</p>
-</li>
-</ul>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Default</th>
-<th>Application</th>
-<th>Description</th>
-<th>Valid Values</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>carbon.compaction.level.threshold</td>
-<td>4, 3</td>
-<td>Minor</td>
-<td>This property is for minor compaction which decides how many segments to be merged. Example: If it is set as 2, 3 then minor compaction will be triggered for every 2 segments. 3 is the number of level 1 compacted segment which is further compacted to new segment.</td>
-<td>NA</td>
-</tr>
-<tr>
-<td>carbon.major.compaction.size</td>
-<td>1024 MB</td>
-<td>Major</td>
-<td>Major compaction size can be configured using this parameter. Sum of the segments which is below this threshold will be merged.</td>
-<td>NA</td>
-</tr>
-<tr>
-<td>carbon.numberof.preserve.segments</td>
-<td>0</td>
-<td>Minor/Major</td>
-<td>If the user wants to preserve some number of segments from being compacted then he can set this property. Example: carbon.numberof.preserve.segments=2 then 2 latest segments will always be excluded from the compaction. No segments will be preserved by default.</td>
-<td>0-100</td>
-</tr>
-<tr>
-<td>carbon.allowed.compaction.days</td>
-<td>0</td>
-<td>Minor/Major</td>
-<td>Compaction will merge the segments which are loaded with in the specific number of days configured. Example: If the configuration is 2, then the segments which are loaded in the time frame of 2 days only will get merged. Segments which are loaded 2 days apart will not be merged.This is disabled by default.</td>
-<td>0-100</td>
-</tr>
-<tr>
-<td>carbon.number.of.cores.while.compacting</td>
-<td>2</td>
-<td>Minor/Major</td>
-<td>Number of cores which is used to write data during compaction.</td>
-<td>0-100</td>
-</tr>
-</tbody>
-</table>
-<p>For compaction commands refer to <a href="ddl.html">DDL operations on CarbonData</a></p>
-
-<script type="text/javascript">
- $('a[href*="#"]:not([href="#"])').click(function() {
-   if (location.pathname.replace(/^\//, '') == this.pathname.replace(/^\//, '') && location.hostname == this.hostname) {
-    var target = $(this.hash);
-    target = target.length ? target : $('[name=' + this.hash.slice(1) + ']');
-    if (target.length) 
-        { $('html, body').animate({    scrollTop: target.offset().top - 52 },100);
-          return false;
-        }
-     }
-  });
-</script>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/ddl-operation-on-carbondata.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/ddl-operation-on-carbondata.html b/src/main/webapp/docs/latest/ddl-operation-on-carbondata.html
new file mode 100644
index 0000000..7886740
--- /dev/null
+++ b/src/main/webapp/docs/latest/ddl-operation-on-carbondata.html
@@ -0,0 +1,186 @@
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+--><h1>DDL Operations on CarbonData</h1><p>This tutorial guides you through the data definition language support provided by CarbonData.</p><h2>Overview</h2><p>The following DDL operations are supported in CarbonData :</p>
+<ul>
+  <li><a href="#create-table">CREATE TABLE</a></li>
+  <li><a href="#show-table">SHOW TABLE</a></li>
+  <li><a href="#drop-table">DROP TABLE</a></li>
+  <li><a href="#compaction">COMPACTION</a></li>
+</ul><h2>CREATE TABLE</h2><p>This command can be used to create a CarbonData table by specifying the list of fields along with the table properties.</p><p><code>
+   CREATE TABLE [IF NOT EXISTS] [db_name.]table_name 
+                    [(col_name data_type , ...)]               
+   STORED BY &#39;carbondata&#39;
+   [TBLPROPERTIES (property_name=property_value, ...)]
+   // All Carbon&#39;s additional table options will go into properties
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>db_name </td>
+      <td>Name of the database. Database name should consist of alphanumeric characters and underscore(_) special character. </td>
+      <td>Yes </td>
+    </tr>
+    <tr>
+      <td>field_list </td>
+      <td>Comma separated List of fields with data type. The field names should consist of alphanumeric characters and underscore(_) special character. </td>
+      <td>No </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in Database. Table Name should consist of alphanumeric characters and underscore(_) special character. </td>
+      <td>No </td>
+    </tr>
+    <tr>
+      <td>STORED BY </td>
+      <td>"org.apache.carbondata.format", identifies and creates a CarbonData table. </td>
+      <td>No </td>
+    </tr>
+    <tr>
+      <td>TBLPROPERTIES </td>
+      <td>List of CarbonData table properties. </td>
+      <td> </td>
+    </tr>
+  </tbody>
+</table><h3>Usage Guidelines</h3><p>Following are the guidelines for using table properties.</p>
+<ul>
+  <li><p><strong>Dictionary Encoding Configuration</strong></p><p>Dictionary encoding is enabled by default for all String columns, and disabled for non-String columns. You can include and exclude columns for dictionary encoding.</p></li>
+</ul><p><code>
+       TBLPROPERTIES (&quot;DICTIONARY_EXCLUDE&quot;=&quot;column1, column2&quot;) 
+       TBLPROPERTIES (&quot;DICTIONARY_INCLUDE&quot;=&quot;column1, column2&quot;) 
+</code></p><p>Here, DICTIONARY_EXCLUDE will exclude dictionary creation. This is applicable for high-cardinality columns and is an optional parameter. DICTIONARY_INCLUDE will generate dictionary for the columns specified in the list.</p>
+<ul>
+  <li><p><strong>Row/Column Format Configuration</strong></p><p>Column groups with more than one column are stored in row format, instead of columnar format. By default, each column is a separate column group.</p></li>
+</ul><p><code>
+TBLPROPERTIES (&quot;COLUMN_GROUPS&quot;=&quot;(column1,column3),
+(Column4,Column5,Column6)&quot;) 
+</code></p>
+<ul>
+  <li><p><strong>Table Block Size Configuration</strong></p><p>The block size of table files can be defined using the property TABLE_BLOCKSIZE. It accepts only integer values. The default value is 1024 MB and supports a range of 1 MB to 2048 MB.  If you do not specify this value in the DDL command , default value is used. </p></li>
+</ul><p><code>
+       TBLPROPERTIES (&quot;TABLE_BLOCKSIZE&quot;=&quot;512 MB&quot;)
+</code></p><p>Here 512 MB means the block size of this table is 512 MB, you can also set it as 512M or 512.</p>
+<ul>
+  <li><p><strong>Inverted Index Configuration</strong></p><p>Inverted index is very useful to improve compression ratio and query speed, especially for those low-cardinality columns who are in reward position.  By default inverted index is enabled. The user can disable the inverted index creation for some columns.</p></li>
+</ul><p><code>
+       TBLPROPERTIES (&quot;NO_INVERTED_INDEX&quot;=&quot;column1,column3&quot;)
+</code></p><p>No inverted index shall be generated for the columns specified in NO_INVERTED_INDEX. This property is applicable on columns with high-cardinality and is an optional parameter.</p><p>NOTE:</p>
+<ul>
+  <li><p>By default all columns other than numeric datatype are treated as dimensions and all columns of numeric datatype are treated as measures.</p></li>
+  <li><p>All dimensions except complex datatype columns are part of multi dimensional key(MDK). This behavior can be overridden by using TBLPROPERTIES. If the user wants to keep any column (except columns of complex datatype) in multi dimensional key then he can keep the columns either in DICTIONARY_EXCLUDE or DICTIONARY_INCLUDE.</p><h3>Example:</h3><p><code>
+   CREATE TABLE IF NOT EXISTS productSchema.productSalesTable (
+                            productNumber Int,
+                            productName String, 
+                            storeCity String, 
+                            storeProvince String, 
+                            productCategory String, 
+                            productBatch String,
+                            saleQuantity Int,
+                            revenue Int)       
+   STORED BY &#39;carbondata&#39; 
+   TBLPROPERTIES (&#39;COLUMN_GROUPS&#39;=&#39;(productName,productCategory)&#39;,
+              &#39;DICTIONARY_EXCLUDE&#39;=&#39;productName&#39;,
+              &#39;DICTIONARY_INCLUDE&#39;=&#39;productNumber&#39;,
+              &#39;NO_INVERTED_INDEX&#39;=&#39;productBatch&#39;)
+</code></p></li>
+</ul><h2>SHOW TABLE</h2><p>This command can be used to list all the tables in current database or all the tables of a specific database. <code>
+  SHOW TABLES [IN db_Name];
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>IN db_Name </td>
+      <td>Name of the database. Required only if tables of this specific database are to be listed. </td>
+      <td>Yes </td>
+    </tr>
+  </tbody>
+</table><h3>Example:</h3><p><code>
+  SHOW TABLES IN ProductSchema;
+</code></p><h2>DROP TABLE</h2><p>This command is used to delete an existing table.</p><p><code>
+  DROP TABLE [IF EXISTS] [db_name.]table_name;
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>db_Name </td>
+      <td>Name of the database. If not specified, current database will be selected. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>Name of the table to be deleted. </td>
+      <td>NO </td>
+    </tr>
+  </tbody>
+</table><h3>Example:</h3><p><code>
+  DROP TABLE IF EXISTS productSchema.productSalesTable;
+</code></p><h2>COMPACTION</h2><p>This command merges the specified number of segments into one segment. This enhances the query performance of the table.</p><p><code>
+  ALTER TABLE [db_name.]table_name COMPACT &#39;MINOR/MAJOR&#39;;
+</code></p><p>To get details about Compaction refer to <a href="data-management.html">Data Management</a></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>db_name </td>
+      <td>Database name, if it is not specified then it uses current database. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in provided database.</td>
+      <td>NO </td>
+    </tr>
+  </tbody>
+</table><h3>Syntax</h3>
+<ul>
+  <li><strong>Minor Compaction</strong></li>
+<p><code>
+ALTER TABLE table_name COMPACT &#39;MINOR&#39;;
+</code>
+</p>
+  <li><strong>Major Compaction</strong></li>
+<p><code>
+ALTER TABLE table_name COMPACT &#39;MAJOR&#39;;
+</code></p>
+</ul>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/ddl.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/ddl.html b/src/main/webapp/docs/latest/ddl.html
deleted file mode 100644
index e270f31..0000000
--- a/src/main/webapp/docs/latest/ddl.html
+++ /dev/null
@@ -1,244 +0,0 @@
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style>
-
-</style></head><body id="preview">
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-“License”); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-&quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-    
-<h1><a id="DDL_Operations_on_CarbonData_0"></a>DDL Operations on CarbonData</h1>
-<p>This tutorial guides you through the data definition language support provided by CarbonData.</p>
-<h2><a id="Overview_3"></a>Overview</h2>
-<p>The following DDL operations are supported in CarbonData :</p>
-<ul>
-<li><a href="#create-table">CREATE TABLE</a></li>
-<li><a href="#show-table">SHOW TABLE</a></li>
-<li><a href="#drop-table">DROP TABLE</a></li>
-<li><a href="#compaction">COMPACTION</a></li>
-</ul>
-<div id="create-table"></div>
-<h2><a id="CREATE_TABLE_11"></a>CREATE TABLE</h2>
-<p>This command can be used to create CarbonData table by specifying the list of fields along with the table properties.</p>
-<pre><code>CREATE TABLE [IF NOT EXISTS] [db_name.]table_name
-                 [(col_name data_type , ...)]
-           STORED BY 'carbondata'
-                 [TBLPROPERTIES (property_name=property_value, ...)]
-                 // All Carbon's additional table options will go into properties
-</code></pre>
-<h3><a id="Parameter_Description_21"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>db_name</td>
-<td>Name of the database. Database name should consist of alphanumeric characters and underscore(_) special character.</td>
-<td>Yes</td>
-</tr>
-<tr>
-<td>field_list</td>
-<td>Comma separated List of fields with data type. The field names should consist of alphanumeric characters and underscore(_) special character.</td>
-<td>No</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in Database. Table Name should consist of alphanumeric characters and underscore(_) special character.</td>
-<td>No</td>
-</tr>
-<tr>
-<td>STORED BY</td>
-<td>“org.apache.carbondata.format”, identifies and creates a CarbonData table.</td>
-<td>No</td>
-</tr>
-<tr>
-<td>TBLPROPERTIES</td>
-<td>List of CarbonData table properties.</td>
-<td></td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Usage_Guideline_31"></a>Usage Guideline</h3>
-<p>Following are the guidelines for using table properties.</p>
-<ul>
-<li>
-<p><strong>Dictionary Encoding Configuration</strong></p>
-<p>Dictionary encoding is enabled by default for all String columns, and disabled for non-String columns. You can include and exclude columns for dictionary encoding.</p>
-<pre><code class="language-ruby"><span class="hljs-constant">TBLPROPERTIES</span> (<span class="hljs-string">"DICTIONARY_EXCLUDE"</span>=<span class="hljs-string">"column1, column2"</span>)
-<span class="hljs-constant">TBLPROPERTIES</span> (<span class="hljs-string">"DICTIONARY_INCLUDE"</span>=<span class="hljs-string">"column1, column2"</span>)
-</code></pre>
-<p>Here, DICTIONARY_EXCLUDE will exclude dictionary creation. This is applicable for high-cardinality columns and is an optional parameter. DICTIONARY_INCLUDE will generate dictionary for the columns specified in the list.</p>
-</li>
-<li>
-<p><strong>Row/Column Format Configuration</strong></p>
-<p>Column groups with more than one column are stored in row format, instead of columnar format. By default, each column is a separate column group.</p>
-<pre><code class="language-ruby"><span class="hljs-constant">TBLPROPERTIES</span> (<span class="hljs-string">"COLUMN_GROUPS"</span>=<span class="hljs-string">"(column1,column3),(Column4,Column5,Column6)"</span>)
-</code></pre>
-</li>
-<li>
-<p><strong>Table Block Size Configuration</strong></p>
-<p>The block size of table files can be defined using the property TABLE_BLOCKSIZE. It accepts only integer values. The default value is 1024 MB and supports a range of 1 MB to 2048 MB. If you do not specify this value in the DDL command, default value is used.</p>
-<pre><code>TBLPROPERTIES (&quot;TABLE_BLOCKSIZE&quot;=&quot;512 MB&quot;)
-</code></pre>
-<p>Here 512 MB means the block size of this table is 512 MB. You can also set it as 512M or 512.</p>
-</li>
-<li>
-<p><strong>Inverted Index Configuration</strong></p>
-<p>Inverted index is very useful to improve compression ratio and query speed, especially for those low-cardinality columns who are in reward position.<br>
-By default inverted index is enabled. The user can disable the inverted index creation for some columns.</p>
-<pre><code>TBLPROPERTIES (&quot;NO_INVERTED_INDEX&quot;=&quot;column1,column3&quot;)
-</code></pre>
-<p>No inverted index shall be generated for the columns specified in NO_INVERTED_INDEX. This property is applicable on columns with high-cardinality and is an optional parameter.</p>
-<p><em>NOTE:</em></p>
-<ul>
-<li>
-<p>By default all columns other than numeric datatype are treated as dimensions and all columns of numeric datatype are treated as measures.</p>
-</li>
-<li>
-<p>All dimensions except complex datatype columns are part of multi dimensional key(MDK). This behavior can be overridden by using TBLPROPERTIES, If the user wants to keep any column (except columns of complex datatype) in multi dimensional key then he can keep the columns either in DICTIONARY_EXCLUDE or DICTIONARY_INCLUDE.</p>
-</li>
-</ul>
-</li>
-</ul>
-<h3><a id="Example_77"></a>Example:</h3>
-<pre><code>CREATE TABLE IF NOT EXISTS productSchema.productSalesTable (
-                             productNumber Int,
-                             productName String,
-                             storeCity String,
-                             storeProvince String,
-                             productCategory String,
-                             productBatch String,
-                             saleQuantity Int,
-                             revenue Int)
-                  STORED BY 'carbondata'
-                  TBLPROPERTIES ('COLUMN_GROUPS'='(productName,productCategory)',
-                                'DICTIONARY_EXCLUDE'='productName',
-                                'DICTIONARY_INCLUDE'='productNumber',
-                                'NO_INVERTED_INDEX'='productBatch')
-</code></pre>
-<div id="show-table"></div>
-<h2><a id="SHOW_TABLE_95"></a>SHOW TABLE</h2>
-<p>This command can be used to list all the tables in current database or all the tables of a specific database.</p>
-<pre><code>SHOW TABLES [IN db_Name];
-</code></pre>
-<h3><a id="Parameter_Description_102"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>IN db_Name</td>
-<td>Name of the database. Required only if tables of this specific database are to be listed.</td>
-<td>Yes</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Example_107"></a>Example:</h3>
-<pre><code>SHOW TABLES IN ProductSchema;
-</code></pre>
-<div id="drop-table"></div>
-<h2><a id="DROP_TABLE_113"></a>DROP TABLE</h2>
-<p>This command is used to delete an existing table.</p>
-<pre><code>DROP TABLE [IF EXISTS] [db_name.]table_name;
-</code></pre>
-<h3><a id="Parameter_Description_121"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>db_Name</td>
-<td>Name of the database. If not specified, current database will be selected.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>Name of the table to be deleted.</td>
-<td>NO</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Example_127"></a>Example:</h3>
-<pre><code>DROP TABLE IF EXISTS productSchema.productSalesTable;
-</code></pre>
-<div id="compaction"></div>
-<h2><a id="COMPACTION_133"></a>COMPACTION</h2>
-<p>This command merges the specified number of segments into one segment. This enhances the query performance of the table.</p>
-<pre><code>ALTER TABLE [db_name.]table_name COMPACT 'MINOR/MAJOR';
-</code></pre>
-<p>To get details about Compaction refer to <a href="data_management.html">Data Management</a></p>
-<h3><a id="Parameter_Description_143"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>db_name</td>
-<td>Database name, if it is not specified then it uses current database.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in provided database.</td>
-<td>NO</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Syntax_150"></a>Syntax</h3>
-<ul>
-<li><strong>Minor Compaction</strong></li>
-</ul>
-<pre><code>ALTER TABLE carbontable COMPACT MINOR;
-</code></pre>
-<ul>
-<li><strong>Major Compaction</strong></li>
-</ul>
-<pre><code>ALTER TABLE carbontable COMPACT MAJOR;
-</code></pre>
-
-<script type="text/javascript">
- $('a[href*="#"]:not([href="#"])').click(function() {
-   if (location.pathname.replace(/^\//, '') == this.pathname.replace(/^\//, '') && location.hostname == this.hostname) {
-    var target = $(this.hash);
-    target = target.length ? target : $('[name=' + this.hash.slice(1) + ']');
-    if (target.length) 
-        { $('html, body').animate({    scrollTop: target.offset().top - 52 },100);
-          return false;
-        }
-     }
-  });
-</script>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/dml-operation-on-carbondata.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/dml-operation-on-carbondata.html b/src/main/webapp/docs/latest/dml-operation-on-carbondata.html
new file mode 100644
index 0000000..b876dae
--- /dev/null
+++ b/src/main/webapp/docs/latest/dml-operation-on-carbondata.html
@@ -0,0 +1,345 @@
+<!--
+    Licensed to the Apache Software Foundation (ASF) under one
+    or more contributor license agreements.  See the NOTICE file
+    distributed with this work for additional information
+    regarding copyright ownership.  The ASF licenses this file
+    to you under the Apache License, Version 2.0 (the
+    "License"); you may not use this file except in compliance
+    with the License.  You may obtain a copy of the License at
+
+      http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing,
+    software distributed under the License is distributed on an
+    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+    KIND, either express or implied.  See the License for the
+    specific language governing permissions and limitations
+    under the License.
+--><h1>DML Operations on CarbonData</h1><p>This tutorial guides you through the data manipulation language support provided by CarbonData.</p><h2>Overview</h2><p>The following DML operations are supported in CarbonData :</p>
+<ul>
+  <li><a href="#load-data">LOAD DATA</a></li>
+  <li><a href="#insert-data-into-a-carbondata-table">INSERT DATA INTO A CARBONDATA TABLE</a></li>
+  <li><a href="#show-segments">SHOW SEGMENTS</a></li>
+  <li><a href="#delete-segment-by-id">DELETE SEGMENT BY ID</a></li>
+  <li><a href="#delete-segment-by-date">DELETE SEGMENT BY DATE</a></li>
+  <li><a href="#update-carbondata-table">UPDATE CARBONDATA TABLE</a></li>
+  <li><a href="#delete-records-from-carbondata-table">DELETE RECORDS FROM CARBONDATA TABLE</a></li>
+</ul><h2>LOAD DATA</h2><p>This command loads the user data in raw format to the CarbonData specific data format store, this allows CarbonData to provide good performance while querying the data. Please visit <a href="data-management.html">Data Management</a> for more details on LOAD.</p><h3>Syntax</h3><p><code>
+LOAD DATA [LOCAL] INPATH &#39;folder_path&#39; 
+INTO TABLE [db_name.]table_name 
+OPTIONS(property_name=property_value, ...)
+</code></p><p>OPTIONS are not mandatory for data loading process. Inside OPTIONS user can provide either of any options like DELIMITER, QUOTECHAR, ESCAPECHAR, MULTILINE as per requirement.</p><p>NOTE: The path shall be canonical path.</p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>folder_path </td>
+      <td>Path of raw csv data folder or file. </td>
+      <td>NO </td>
+    </tr>
+    <tr>
+      <td>db_name </td>
+      <td>Database name, if it is not specified then it uses the current database. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in provided database. </td>
+      <td>NO </td>
+    </tr>
+    <tr>
+      <td>OPTIONS </td>
+      <td>Extra options provided to Load </td>
+      <td>YES </td>
+    </tr>
+  </tbody>
+</table><h3>Usage Guidelines</h3><p>You can use the following options to load data:</p>
+<ul>
+  <li><p><strong>DELIMITER:</strong> Delimiters can be provided in the load command.</p><p><code>
+OPTIONS(&#39;DELIMITER&#39;=&#39;,&#39;)
+</code></p></li>
+  <li><p><strong>QUOTECHAR:</strong> Quote Characters can be provided in the load command.</p><p><code>
+OPTIONS(&#39;QUOTECHAR&#39;=&#39;&quot;&#39;)
+</code></p></li>
+  <li><p><strong>COMMENTCHAR:</strong> Comment Characters can be provided in the load command if user want to comment lines.</p><p><code>
+OPTIONS(&#39;COMMENTCHAR&#39;=&#39;#&#39;)
+</code></p></li>
+  <li><p><strong>FILEHEADER:</strong> Headers can be provided in the LOAD DATA command if headers are missing in the source files.</p><p><code>
+OPTIONS(&#39;FILEHEADER&#39;=&#39;column1,column2&#39;) 
+</code></p></li>
+  <li><p><strong>MULTILINE:</strong> CSV with new line character in quotes.</p><p><code>
+OPTIONS(&#39;MULTILINE&#39;=&#39;true&#39;) 
+</code></p></li>
+  <li><p><strong>ESCAPECHAR:</strong> Escape char can be provided if user want strict validation of escape character on CSV.</p><p><code>
+OPTIONS(&#39;ESCAPECHAR&#39;=&#39;\&#39;) 
+</code></p></li>
+  <li><p><strong>COMPLEX_DELIMITER_LEVEL_1:</strong> Split the complex type data column in a row (eg., a$b$c --&gt; Array = {a,b,c}).</p><p><code>
+OPTIONS(&#39;COMPLEX_DELIMITER_LEVEL_1&#39;=&#39;$&#39;) 
+</code></p></li>
+  <li><p><strong>COMPLEX_DELIMITER_LEVEL_2:</strong> Split the complex type nested data column in a row. Applies level_1 delimiter &amp; applies level_2 based on complex data type (eg., a:b$c:d --&gt; Array&gt; = {{a,b},{c,d}}).</p><p><code>
+OPTIONS(&#39;COMPLEX_DELIMITER_LEVEL_2&#39;=&#39;:&#39;) 
+</code></p></li>
+  <li><p><strong>ALL_DICTIONARY_PATH:</strong> All dictionary files path.</p><p><code>
+OPTIONS(&#39;ALL_DICTIONARY_PATH&#39;=&#39;/opt/alldictionary/data.dictionary&#39;)
+</code></p></li>
+  <li><p><strong>COLUMNDICT:</strong> Dictionary file path for specified column.</p><p><code>
+OPTIONS(&#39;COLUMNDICT&#39;=&#39;column1:dictionaryFilePath1,
+column2:dictionaryFilePath2&#39;)
+</code></p><p>NOTE: ALL_DICTIONARY_PATH and COLUMNDICT can't be used together.</p></li>
+  <li><p><strong>DATEFORMAT:</strong> Date format for specified column.</p><p><code>
+OPTIONS(&#39;DATEFORMAT&#39;=&#39;column1:dateFormat1, column2:dateFormat2&#39;)
+</code></p><p>NOTE: Date formats are specified by date pattern strings. The date pattern letters in CarbonData are same as in JAVA. Refer to <a href="http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html">SimpleDateFormat</a>.</p></li>
+</ul><h3>Example:</h3><p><code>
+LOAD DATA local inpath &#39;/opt/rawdata/data.csv&#39; INTO table carbontable
+options(&#39;DELIMITER&#39;=&#39;,&#39;, &#39;QUOTECHAR&#39;=&#39;&quot;&#39;,&#39;COMMENTCHAR&#39;=&#39;#&#39;,
+&#39;FILEHEADER&#39;=&#39;empno,empname,designation,doj,workgroupcategory,
+ workgroupcategoryname,deptno,deptname,projectcode,
+ projectjoindate,projectenddate,attendance,utilization,salary&#39;,
+&#39;MULTILINE&#39;=&#39;true&#39;,&#39;ESCAPECHAR&#39;=&#39;\&#39;,&#39;COMPLEX_DELIMITER_LEVEL_1&#39;=&#39;$&#39;, 
+&#39;COMPLEX_DELIMITER_LEVEL_2&#39;=&#39;:&#39;,
+&#39;ALL_DICTIONARY_PATH&#39;=&#39;/opt/alldictionary/data.dictionary&#39;
+)
+</code></p><h2>INSERT DATA INTO A CARBONDATA TABLE</h2><p>This command inserts data into a CarbonData table. It is defined as a combination of two queries Insert and Select query respectively. It inserts records from a source table into a target CarbonData table. The source table can be a Hive table, Parquet table or a CarbonData table itself. It comes with the functionality to aggregate the records of a table by performing Select query on source table and load its corresponding resultant records into a CarbonData table.</p><p><strong>NOTE</strong> : The client node where the INSERT command is executing, must be part of the cluster.</p><h3>Syntax</h3><p><code>
+INSERT INTO TABLE &lt;CARBONDATA TABLE&gt; SELECT * FROM sourceTableName 
+[ WHERE { &lt;filter_condition&gt; } ];
+</code></p><p>You can also omit the <code>table</code> keyword and write your query as:</p><p><code>
+INSERT INTO &lt;CARBONDATA TABLE&gt; SELECT * FROM sourceTableName 
+[ WHERE { &lt;filter_condition&gt; } ];
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>CARBON TABLE </td>
+      <td>The name of the Carbon table in which you want to perform the insert operation. </td>
+    </tr>
+    <tr>
+      <td>sourceTableName </td>
+      <td>The table from which the records are read and inserted into destination CarbonData table. </td>
+    </tr>
+  </tbody>
+</table><h3>Usage Guidelines</h3><p>The following condition must be met for successful insert operation :</p>
+<ul>
+  <li>The source table and the CarbonData table must have the same table schema.</li>
+  <li>The table must be created.</li>
+  <li>Overwrite is not supported for CarbonData table.</li>
+  <li>The data type of source and destination table columns should be same, else the data from source table will be treated as bad records and the INSERT command fails.</li>
+  <li>INSERT INTO command does not support partial success if bad records are found, it will fail.</li>
+  <li>Data cannot be loaded or updated in source table while insert from source table to target table is in progress.</li>
+</ul><p>To enable data load or update during insert operation, configure the following property to true.</p><p><code>
+carbon.insert.persist.enable=true
+</code></p><p>By default the above configuration will be false.</p><p><strong>NOTE</strong>: Enabling this property will reduce the performance.</p><h3>Examples</h3><p><code>
+INSERT INTO table1 SELECT item1 ,sum(item2 + 1000) as result FROM 
+table2 group by item1;
+</code></p><p><code>
+INSERT INTO table1 SELECT item1, item2, item3 FROM table2 
+where item2=&#39;xyz&#39;;
+</code></p><p><code>
+INSERT INTO table1 SELECT * FROM table2 
+where exists (select * from table3 
+where table2.item1 = table3.item1);
+</code></p><p><strong>The Status Success/Failure shall be captured in the driver log.</strong></p><h2>SHOW SEGMENTS</h2><p>This command is used to get the segments of CarbonData table.</p><p><code>
+SHOW SEGMENTS FOR TABLE [db_name.]table_name 
+LIMIT number_of_segments;
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>db_name </td>
+      <td>Database name, if it is not specified then it uses the current database. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in provided database. </td>
+      <td>NO </td>
+    </tr>
+    <tr>
+      <td>number_of_segments </td>
+      <td>Limit the output to this number. </td>
+      <td>YES </td>
+    </tr>
+  </tbody>
+</table><h3>Example:</h3><p><code>
+SHOW SEGMENTS FOR TABLE CarbonDatabase.CarbonTable LIMIT 4;
+</code></p><h2>DELETE SEGMENT BY ID</h2><p>This command is used to delete segment by using the segment ID. Each segment has a unique segment ID associated with it. Using this segment ID, you can remove the segment.</p><p>The following command will get the segmentID.</p><p><code>
+SHOW SEGMENTS FOR Table dbname.tablename LIMIT number_of_segments
+</code></p><p>After you retrieve the segment ID of the segment that you want to delete, execute the following command to delete the selected segment.</p><p><code>
+DELETE SEGMENT segment_sequence_id1, segments_sequence_id2, .... 
+FROM TABLE tableName
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>segment_id </td>
+      <td>Segment Id of the load. </td>
+      <td>NO </td>
+    </tr>
+    <tr>
+      <td>db_name </td>
+      <td>Database name, if it is not specified then it uses the current database. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in provided database. </td>
+      <td>NO </td>
+    </tr>
+  </tbody>
+</table><h3>Example:</h3><p><code>
+DELETE SEGMENT 0 FROM TABLE CarbonDatabase.CarbonTable;
+DELETE SEGMENT 0.1,5,8 FROM TABLE CarbonDatabase.CarbonTable;
+</code>  NOTE: Here 0.1 is compacted segment sequence id. </p><h2>DELETE SEGMENT BY DATE</h2><p>This command will allow to delete the CarbonData segment(s) from the store based on the date provided by the user in the DML command. The segment created before the particular date will be removed from the specific stores.</p><p><code>
+DELETE FROM TABLE [schema_name.]table_name 
+WHERE[DATE_FIELD]BEFORE [DATE_VALUE]
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+      <th>Optional </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>DATE_VALUE </td>
+      <td>Valid segment load start time value. All the segments before this specified date will be deleted. </td>
+      <td>NO </td>
+    </tr>
+    <tr>
+      <td>db_name </td>
+      <td>Database name, if it is not specified then it uses the current database. </td>
+      <td>YES </td>
+    </tr>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the table in provided database. </td>
+      <td>NO </td>
+    </tr>
+  </tbody>
+</table><h3>Example:</h3><p><code>
+ DELETE SEGMENTS FROM TABLE CarbonDatabase.CarbonTable 
+ WHERE STARTTIME BEFORE &#39;2017-06-01 12:05:06&#39;;  
+</code></p><h2>Update CarbonData Table</h2><p>This command will allow to update the carbon table based on the column expression and optional filter conditions.</p><h3>Syntax</h3><p><code>
+ UPDATE &lt;table_name&gt;
+ SET (column_name1, column_name2, ... column_name n) =
+ (column1_expression , column2_expression . .. column n_expression )
+ [ WHERE { &lt;filter_condition&gt; } ];
+</code></p><p>alternatively the following the command can also be used for updating the CarbonData Table :</p><p><code>
+UPDATE &lt;table_name&gt;
+SET (column_name1, column_name2,) =
+(select sourceColumn1, sourceColumn2 from sourceTable
+[ WHERE { &lt;filter_condition&gt; } ] )
+[ WHERE { &lt;filter_condition&gt; } ];
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the Carbon table in which you want to perform the update operation. </td>
+    </tr>
+    <tr>
+      <td>column_name </td>
+      <td>The destination columns to be updated. </td>
+    </tr>
+    <tr>
+      <td>sourceColumn </td>
+      <td>The source table column values to be updated in destination table. </td>
+    </tr>
+    <tr>
+      <td>sourceTable </td>
+      <td>The table from which the records are updated into destination Carbon table. </td>
+    </tr>
+  </tbody>
+</table><h3>Usage Guidelines</h3><p>The following conditions must be met for successful updation :</p>
+<ul>
+  <li>The update command fails if multiple input rows in source table are matched with single row in destination table.</li>
+  <li>If the source table generates empty records, the update operation will complete successfully without updating the table.</li>
+  <li>If a source table row does not correspond to any of the existing rows in a destination table, the update operation will complete successfully without updating the table.</li>
+  <li>In sub-query, if the source table and the target table are same, then the update operation fails.</li>
+  <li>If the sub-query used in UPDATE statement contains aggregate method or group by query, then the UPDATE operation fails.</li>
+</ul><h3>Examples</h3><p>Update is not supported for queries that contain aggregate or group by.</p><p><code>
+ UPDATE t_carbn01 a
+ SET (a.item_type_code, a.profit) = ( SELECT b.item_type_cd,
+ sum(b.profit) from t_carbn01b b
+ WHERE item_type_cd =2 group by item_type_code);
+</code></p><p>Here the Update Operation fails as the query contains aggregate function sum(b.profit) and group by clause in the sub-query.</p><p><code>
+UPDATE carbonTable1 d
+SET(d.column3,d.column5 ) = (SELECT s.c33 ,s.c55
+FROM sourceTable1 s WHERE d.column1 = s.c11)
+WHERE d.column1 = &#39;china&#39; EXISTS( SELECT * from table3 o where o.c2 &gt; 1);
+</code></p><p><code>
+UPDATE carbonTable1 d SET (c3) = (SELECT s.c33 from sourceTable1 s
+WHERE d.column1 = s.c11)
+WHERE exists( select * from iud.other o where o.c2 &gt; 1);
+</code></p><p><code>
+UPDATE carbonTable1 SET (c2, c5 ) = (c2 + 1, concat(c5 , &quot;y&quot; ));
+</code></p><p><code>
+UPDATE carbonTable1 d SET (c2, c5 ) = (c2 + 1, &quot;xyx&quot;)
+WHERE d.column1 = &#39;india&#39;;
+</code></p><p><code>
+UPDATE carbonTable1 d SET (c2, c5 ) = (c2 + 1, &quot;xyx&quot;)
+WHERE d.column1 = &#39;india&#39;
+and EXISTS( SELECT * FROM table3 o WHERE o.column2 &gt; 1);
+</code></p><p><strong>The Status Success/Failure shall be captured in the driver log and the client.</strong></p><h2>Delete Records from CarbonData Table</h2><p>This command allows us to delete records from CarbonData table.</p><h3>Syntax</h3><p><code>
+DELETE FROM table_name [WHERE expression];
+</code></p><h3>Parameter Description</h3>
+<table class="table table-striped table-bordered">
+  <thead>
+    <tr>
+      <th>Parameter </th>
+      <th>Description </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td>table_name </td>
+      <td>The name of the Carbon table in which you want to perform the delete. </td>
+    </tr>
+  </tbody>
+</table><h3>Examples</h3><p><code>
+DELETE FROM columncarbonTable1 d WHERE d.column1  = &#39;china&#39;;
+</code></p><p><code>
+DELETE FROM dest WHERE column1 IN (&#39;china&#39;, &#39;USA&#39;);
+</code></p><p><code>
+DELETE FROM columncarbonTable1
+WHERE column1 IN (SELECT column11 FROM sourceTable2);
+</code></p><p><code>
+DELETE FROM columncarbonTable1
+WHERE column1 IN (SELECT column11 FROM sourceTable2 WHERE
+column1 = &#39;USA&#39;);
+</code></p><p><code>
+DELETE FROM columncarbonTable1 WHERE column2 &gt;= 4
+</code></p><p><strong>The Status Success/Failure shall be captured in the driver log and the client.</strong></p>
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b427c61c/src/main/webapp/docs/latest/dml.html
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/latest/dml.html b/src/main/webapp/docs/latest/dml.html
deleted file mode 100644
index 454993c..0000000
--- a/src/main/webapp/docs/latest/dml.html
+++ /dev/null
@@ -1,276 +0,0 @@
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style>
-
-</style></head><body id="preview">
-<!--
-Licensed to the Apache Software Foundation (ASF) under one
-or more contributor license agreements.  See the NOTICE file
-distributed with this work for additional information
-regarding copyright ownership.  The ASF licenses this file
-to you under the Apache License, Version 2.0 (the
-“License”); you may not use this file except in compliance
-with the License.  You may obtain a copy of the License at
- http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing,
-software distributed under the License is distributed on an
-&quot;AS IS&quot; BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-KIND, either express or implied.  See the License for the
-specific language governing permissions and limitations
-under the License.
--->
-
-    
-<h1><a id="DML_Operations_on_CarbonData_0"></a>DML Operations on CarbonData</h1>
-<p>This tutorial guides you through the data manipulation language support provided by CarbonData.</p>
-<h2><a id="Overview_3"></a>Overview</h2>
-<p>The following DML operations are supported in CarbonData :</p>
-<ul>
-<li><a href="#load-data">LOAD DATA</a></li>
-<li><a href="#show-segments">SHOW SEGMENTS</a></li>
-<li><a href="#delete-segment-by-id">DELETE SEGMENT BY ID</a></li>
-<li><a href="#delete-segment-by-date">DELETE SEGMENT BY DATE</a></li>
-</ul>
-<div id="load-data"></div>
-<h2><a id="LOAD_DATA_11"></a>LOAD DATA</h2>
-<p>This command loads the user data in raw format to the CarbonData specific data format store, this allows CarbonData to provides good performance while querying the data. Please visit <a href="data_management.html">Data Management</a> for more details on LOAD.</p>
-<h3><a id="Syntax_16"></a>Syntax</h3>
-<pre><code>LOAD DATA [LOCAL] INPATH 'folder_path' INTO TABLE [db_name.]table_name OPTIONS(property_name=property_value, ...)
-</code></pre>
-<p>OPTIONS are not mandatory for data loading process. Inside OPTIONS user can provide either of any options like DELIMITER, QUOTECHAR, ESCAPECHAR, MULTILINE as per requirement.</p>
-<p>NOTE: The path shall be canonical path.</p>
-<h3><a id="Parameter_Description_26"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>folder_path</td>
-<td>Path of raw csv data folder or file.</td>
-<td>NO</td>
-</tr>
-<tr>
-<td>db_name</td>
-<td>Database name, if it is not specified then it uses current database.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in provided database.</td>
-<td>NO</td>
-</tr>
-<tr>
-<td>OPTIONS</td>
-<td>Extra options provided to Load</td>
-<td>YES</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Usage_Guideline_36"></a>Usage Guidelines</h3>
-<p>You can use the following options to load data:</p>
-<ul>
-<li>
-<p><strong>DELIMITER:</strong> Delimiters can be provided in the load command.</p>
-<pre><code>OPTIONS('DELIMITER'=',')
-</code></pre>
-</li>
-<li>
-<p><strong>QUOTECHAR:</strong> Quote Characters can be provided in the load command.</p>
-<pre><code>OPTIONS('QUOTECHAR'='&quot;')
-</code></pre>
-</li>
-<li>
-<p><strong>COMMENTCHAR:</strong> Comment Characters can be provided in the load command if user want to comment lines.</p>
-<pre><code>OPTIONS('COMMENTCHAR'='#')
-</code></pre>
-</li>
-<li>
-<p><strong>FILEHEADER:</strong> Headers can be provided in the LOAD DATA command if headers are missing in the source files.</p>
-<pre><code>OPTIONS('FILEHEADER'='column1,column2')
-</code></pre>
-</li>
-<li>
-<p><strong>MULTILINE:</strong> CSV with new line character in quotes.</p>
-<pre><code>OPTIONS('MULTILINE'='true')
-</code></pre>
-</li>
-<li>
-<p><strong>ESCAPECHAR:</strong> Escape char can be provided if user want strict validation of escape character on CSV.</p>
-<pre><code>OPTIONS('ESCAPECHAR'='\')
-</code></pre>
-</li>
-<li>
-<p><strong>COMPLEX_DELIMITER_LEVEL_1:</strong> Split the complex type data column in a row (eg., a$b$c --&gt; Array = {a,b,c}).</p>
-<pre><code>OPTIONS('COMPLEX_DELIMITER_LEVEL_1'='$')
-</code></pre>
-</li>
-<li>
-<p><strong>COMPLEX_DELIMITER_LEVEL_2:</strong> Split the complex type nested data column in a row. Applies level_1 delimiter &amp; applies level_2 based on complex data type (eg., a:b$c:d --&gt; Array&gt; = {{a,b},{c,d}}).</p>
-<pre><code>OPTIONS('COMPLEX_DELIMITER_LEVEL_2'=':')
-</code></pre>
-</li>
-<li>
-<p><strong>ALL_DICTIONARY_PATH:</strong> All dictionary files path.</p>
-<pre><code>OPTIONS('ALL_DICTIONARY_PATH'='/opt/alldictionary/data.dictionary')
-</code></pre>
-</li>
-<li>
-<p><strong>COLUMNDICT:</strong> Dictionary file path for specified column.</p>
-<pre><code>OPTIONS('COLUMNDICT'='column1:dictionaryFilePath1, column2:dictionaryFilePath2')
-</code></pre>
-<p>NOTE: ALL_DICTIONARY_PATH and COLUMNDICT can’t be used together.</p>
-</li>
-<li>
-<p><strong>DATEFORMAT:</strong> Date format for specified column.</p>
-<pre><code>OPTIONS('DATEFORMAT'='column1:dateFormat1, column2:dateFormat2')
-</code></pre>
-<p>NOTE: Date formats are specified by date pattern strings. The date pattern letters in CarbonData are<br>
-the same as in JAVA. Refer to <a href="http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html">SimpleDateFormat</a>.</p>
-</li>
-</ul>
-<h3><a id="Example_100"></a>Example:</h3>
-<pre><code>LOAD DATA local inpath '/opt/rawdata/data.csv' INTO table carbontable
-                         options('DELIMITER'=',', 'QUOTECHAR'='&quot;', 'COMMENTCHAR'='#',
-                                 'FILEHEADER'='empno,empname,
- designation,doj,workgroupcategory,
- workgroupcategoryname,deptno,deptname,projectcode,
- projectjoindate,projectenddate,attendance,utilization,salary',
-                                 'MULTILINE'='true', 'ESCAPECHAR'='\',
- 'COMPLEX_DELIMITER_LEVEL_1'='$',
-                                 'COMPLEX_DELIMITER_LEVEL_2'=':',
-                                 'ALL_DICTIONARY_PATH'='/opt/alldictionary/data.dictionary'
-                                 )
-
-</code></pre>
-<div id="show-segments">
-</div>
-<h2><a id="SHOW_SEGMENTS_117"></a>SHOW SEGMENTS</h2>
-<p>This command is used to get the segments of CarbonData table.</p>
-<pre><code>SHOW SEGMENTS FOR TABLE [db_name.]table_name LIMIT number_of_segments;
-</code></pre>
-<h3><a id="Parameter_Description_125"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>db_name</td>
-<td>Database name, if it is not specified then it uses current database.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in provided database.</td>
-<td>NO</td>
-</tr>
-<tr>
-<td>number_of_segments</td>
-<td>Limit the output to this number.</td>
-<td>YES</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Example_133"></a>Example:</h3>
-<pre><code>SHOW SEGMENTS FOR TABLE CarbonDatabase.CarbonTable LIMIT 4;
-</code></pre>
-<div id="delete-segment-by-id"></div>
-<h2><a id="DELETE_SEGMENT_BY_ID_138"></a>DELETE SEGMENT BY ID</h2>
-<p>This command is used to delete segment by using the segment ID. Each segment has a unique segment ID associated with it. Using this segment ID, you can remove the segment.</p>
-<p>The following command will get the segmentID.</p>
-<pre><code>SHOW SEGMENTS FOR Table dbname.tablename LIMIT number_of_segments
-</code></pre>
-<p>After you retrieve the segment ID of the segment that you want to delete, execute the following command to delete the selected segment.</p>
-<pre><code>DELETE SEGMENT segment_sequence_id1, segments_sequence_id2, .... FROM TABLE tableName
-</code></pre>
-<h3><a id="Parameter_Description_152"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>segment_id</td>
-<td>Segment Id of the load.</td>
-<td>NO</td>
-</tr>
-<tr>
-<td>db_name</td>
-<td>Database name, if it is not specified then it uses current database.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in provided database.</td>
-<td>NO</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Example_159"></a>Example:</h3>
-<pre><code>DELETE SEGMENT 0 FROM TABLE CarbonDatabase.CarbonTable;
-DELETE SEGMENT 0.1,5,8 FROM TABLE CarbonDatabase.CarbonTable;
-</code></pre>
-<p>NOTE: Here 0.1 is compacted segment sequence id.</p>
-
-<div id="delete-segment-by-date"></div>
-<h2><a id="DELETE_SEGMENT_BY_DATE_166"></a>DELETE SEGMENT BY DATE</h2>
-<p>This command will allow to delete the CarbonData segment(s) from the store based on the date provided by the user in the DML command. The segment created before the particular date will be removed from the specific stores.</p>
-<pre><code>DELETE FROM TABLE [schema_name.]table_name WHERE[DATE_FIELD]BEFORE [DATE_VALUE]
-</code></pre>
-<h3><a id="Parameter_Description_175"></a>Parameter Description</h3>
-<table class="table table-striped table-bordered">
-<thead>
-<tr>
-<th>Parameter</th>
-<th>Description</th>
-<th>Optional</th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td>DATE_VALUE</td>
-<td>Valid segement load start time value. All the segments before this specified date will be deleted.</td>
-<td>NO</td>
-</tr>
-<tr>
-<td>db_name</td>
-<td>Database name, if it is not specified then it uses current database.</td>
-<td>YES</td>
-</tr>
-<tr>
-<td>table_name</td>
-<td>The name of the table in provided database.</td>
-<td>NO</td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Example_183"></a>Example:</h3>
-<pre><code>DELETE SEGMENTS FROM TABLE CarbonDatabase.CarbonTable WHERE STARTTIME BEFORE '2017-06-01 12:05:06';
-</code></pre>
-
-<script type="text/javascript">
- $('a[href*="#"]:not([href="#"])').click(function() {
-   if (location.pathname.replace(/^\//, '') == this.pathname.replace(/^\//, '') && location.hostname == this.hostname) {
-    var target = $(this.hash);
-    target = target.length ? target : $('[name=' + this.hash.slice(1) + ']');
-    if (target.length) 
-        { $('html, body').animate({    scrollTop: target.offset().top - 52 },100);
-          return false;
-        }
-     }
-  });
-</script>
-
-</body></html>



Mime
View raw message