carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ravipes...@apache.org
Subject [12/50] [abbrv] incubator-carbondata git commit: [CARBONDATA-624] Complete CarbonData document in md files
Date Fri, 20 Jan 2017 17:39:20 GMT
[CARBONDATA-624] Complete CarbonData document in md files


Project: http://git-wip-us.apache.org/repos/asf/incubator-carbondata/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-carbondata/commit/276a6111
Tree: http://git-wip-us.apache.org/repos/asf/incubator-carbondata/tree/276a6111
Diff: http://git-wip-us.apache.org/repos/asf/incubator-carbondata/diff/276a6111

Branch: refs/heads/branch-1.0
Commit: 276a6111e40c2ed02da443130d64781240e2ea3c
Parents: e6fa4ad
Author: sgururajshetty <sgururajshetty@gmail.com>
Authored: Wed Jan 18 21:20:10 2017 +0530
Committer: ravipesala <ravi.pesala@gmail.com>
Committed: Wed Jan 18 21:20:10 2017 +0530

----------------------------------------------------------------------
 ...Building-CarbonData-And-IDE-Configuartion.md |   73 -
 docs/Carbon-Packaging-and-Interfaces.md         |   91 --
 docs/Carbondata-File-Structure-and-Format.md    |   55 -
 docs/DDL-Operations-on-Carbon.md                |  187 ---
 docs/DML-Operations-on-Carbon.md                |  197 ---
 docs/Data-Management.md                         |  255 ++--
 docs/Quick-Start.md                             |   89 --
 docs/configuration-parameters.md                |  149 ++
 docs/ddl-operation-on-carbondata.md             |  193 +++
 docs/dml-operation-on-carbondata.md             |  429 ++++++
 docs/faq.md                                     |   47 +
 docs/images/CarbonData_logo.png                 |  Bin 0 -> 10971 bytes
 docs/images/carbon_data_file_structure_new.png  |  Bin 0 -> 78374 bytes
 docs/images/carbon_data_format_new.png          |  Bin 0 -> 73708 bytes
 docs/images/carbon_data_full_scan.png           |  Bin 0 -> 35710 bytes
 docs/images/carbon_data_motivation.png          |  Bin 0 -> 25388 bytes
 docs/images/carbon_data_olap_scan.png           |  Bin 0 -> 45235 bytes
 docs/images/carbon_data_random_scan.png         |  Bin 0 -> 46317 bytes
 docs/images/format/CarbonData_logo.png          |  Bin 10971 -> 0 bytes
 .../format/carbon_data_file_structure_new.png   |  Bin 78374 -> 0 bytes
 docs/images/format/carbon_data_format_new.png   |  Bin 73708 -> 0 bytes
 docs/images/format/carbon_data_full_scan.png    |  Bin 35710 -> 0 bytes
 docs/images/format/carbon_data_motivation.png   |  Bin 25388 -> 0 bytes
 docs/images/format/carbon_data_olap_scan.png    |  Bin 45235 -> 0 bytes
 docs/images/format/carbon_data_random_scan.png  |  Bin 46317 -> 0 bytes
 docs/installation-guide.md                      |  187 +++
 docs/overview-of-carbondata.md                  |  178 +++
 docs/quick-start-guide.md                       |  178 +++
 docs/table-of-content.md                        |   47 +
 docs/troubleshooting.md                         |   30 +
 docs/use-cases-of-carbondata.md                 |   77 +
 docs/useful-tips-on-carbondata.md               |  180 +++
 docs/user-guide-toc.md                          |   47 +
 docs/using-carbondata.md                        |   35 +
 log.txt                                         | 1363 ++++++++++++++++++
 35 files changed, 3271 insertions(+), 816 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/Building-CarbonData-And-IDE-Configuartion.md
----------------------------------------------------------------------
diff --git a/docs/Building-CarbonData-And-IDE-Configuartion.md b/docs/Building-CarbonData-And-IDE-Configuartion.md
deleted file mode 100644
index 941bcc3..0000000
--- a/docs/Building-CarbonData-And-IDE-Configuartion.md
+++ /dev/null
@@ -1,73 +0,0 @@
-<!--
-    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.
--->
-
-### Building CarbonData
-Prerequisites for building CarbonData:
-* Unix-like environment (Linux, Mac OS X)
-* [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
-* [Apache Maven (we recommend version 3.3 or later)](https://maven.apache.org/download.cgi)
-* [Java 7 or 8](http://www.oracle.com/technetwork/java/javase/downloads/index.html)
-* Scala 2.10
-* [Apache Thrift 0.9.3](https://thrift.apache.org/download)
-
-I. Clone CarbonData
-```
-$ git clone https://github.com/apache/incubator-carbondata.git
-```
-II. Build the project 
-* Build without test.By default carbon takes Spark 1.5.2 to build the project
-```
-$ mvn -DskipTests clean package 
-```
-* Build with different spark versions
-```
-$ mvn -DskipTests -Pspark-1.5 -Dspark.version=1.5.0 clean package
-$ mvn -DskipTests -Pspark-1.5 -Dspark.version=1.5.1 clean package
-$ mvn -DskipTests -Pspark-1.5 -Dspark.version=1.5.2 clean package
- 
-$ mvn -DskipTests -Pspark-1.6 -Dspark.version=1.6.0 clean package
-$ mvn -DskipTests -Pspark-1.6 -Dspark.version=1.6.1 clean package
-$ mvn -DskipTests -Pspark-1.6 -Dspark.version=1.6.2 clean package
-```
-* Build the assembly jar which includes Spark and Hadoop jars
-```
-$ mvn clean -DskipTests -Pinclude-all package
-```
-* Build with test
-```
-$ mvn clean package
-```
-
-### Developing CarbonData
-The CarbonData committers use IntelliJ IDEA and Eclipse IDE to develop.
-
-#### IntelliJ IDEA
-* Download IntelliJ at https://www.jetbrains.com/idea/ and install the Scala plug-in for IntelliJ at http://plugins.jetbrains.com/plugin/?id=1347
-* Go to "File -> Import Project", locate the CarbonData source directory, and select "Maven Project".
-* In the Import Wizard, select "Import Maven projects automatically" and leave other settings at their default. 
-* Leave other settings at their default and you should be able to start your development.
-* When you run the scala test, sometimes you will get out of memory exception. You can increase your VM memory usage by the following setting, for example:
-```
--XX:MaxPermSize=512m -Xmx3072m
-```
-You can also make those setting to be the default by setting to the "Defaults -> ScalaTest".
-
-#### Eclipse
-* Download the Scala IDE (preferred) or install the scala plugin to Eclipse.
-* Import the CarbonData Maven projects ("File" -> "Import" -> "Maven" -> "Existing Maven Projects" -> locate the CarbonData source directory).

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/Carbon-Packaging-and-Interfaces.md
----------------------------------------------------------------------
diff --git a/docs/Carbon-Packaging-and-Interfaces.md b/docs/Carbon-Packaging-and-Interfaces.md
deleted file mode 100644
index c114c8f..0000000
--- a/docs/Carbon-Packaging-and-Interfaces.md
+++ /dev/null
@@ -1,91 +0,0 @@
-<!--
-    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.
--->
-
-## Packaging
-Carbon provides following JAR packages:
-
-![carbon modules2](https://cloud.githubusercontent.com/assets/6500698/14255195/831c6e90-fac5-11e5-87ab-3b16d84918fb.png)
-
-- **carbon-store.jar or carbondata-assembly.jar:** This is the main Jar for carbon project, the target user of it are both user and developer. 
-      - For MapReduce application users, this jar provides API to read and write carbon files through CarbonInput/OutputFormat in carbon-hadoop module.
-      - For developer, this jar can be used to integrate carbon with processing engine like spark and hive, by leveraging API in carbon-processing module.
-
-- **carbon-spark.jar(Currently it is part of assembly jar):** provides support for spark user, spark user can manipulate carbon data files by using native spark DataFrame/SQL interface. Apart from this, in order to leverage carbon's builtin lifecycle management function, higher level concept like Managed Carbon Table, Database and corresponding DDL are introduced.
-
-- **carbon-hive.jar(not yet provided):** similar to carbon-spark, which provides integration to carbon and hive.
-
-## API
-Carbon can be used in following scenarios:
-### 1. For MapReduce application user
-This User API is provided by carbon-hadoop. In this scenario, user can process carbon files in his MapReduce application by choosing CarbonInput/OutputFormat, and is responsible using it correctly.Currently only CarbonInputFormat is provided and OutputFormat will be provided soon.
-
-
-### 2. For Spark user 
-This User API is provided by the Spark itself. There are also two levels of APIs
--  **Carbon File**
-
-Similar to parquet, json, or other data source in Spark, carbon can be used with data source API. For example(please refer to DataFrameAPIExample for the more detail):
-```
-// User can create a DataFrame from any data source or transformation.
-val df = ...
-
-// Write data
-// User can write a DataFrame to a carbon file
- df.write
-   .format("carbondata")
-   .option("tableName", "carbontable")
-   .mode(SaveMode.Overwrite)
-   .save()
-
-
-// read carbon data by data source API
-df = carbonContext.read
-  .format("carbondata")
-  .option("tableName", "carbontable")
-  .load("/path")
-
-// User can then use DataFrame for analysis
-df.count
-SVMWithSGD.train(df, numIterations)
-
-// User can also register the DataFrame with a table name, and use SQL for analysis
-df.registerTempTable("t1")  // register temporary table in SparkSQL catalog
-df.registerHiveTable("t2")  // Or, use a implicit funtion to register to Hive metastore
-sqlContext.sql("select count(*) from t1").show
-```
-
-- **Managed Carbon Table**
-
-Since carbon has builtin support for high level concept like Table, Database, and supports full data lifecycle management, instead of dealing with just files, user can use carbon specific DDL to manipulate data in Table and Database level. Please refer [DDL](https://github.com/HuaweiBigData/carbondata/wiki/Language-Manual:-DDL) and [DML] (https://github.com/HuaweiBigData/carbondata/wiki/Language-Manual:-DML)
-
-For example:
-```
-// Use SQL to manage table and query data
-create database db1;
-use database db1;
-show databases;
-create table tbl1 using org.apache.carbondata.spark;
-load data into table tlb1 path 'some_files';
-select count(*) from tbl1;
-```
-
-### 3. For developer
-For developer who want to integrate carbon into a processing engine like spark/hive/flink, use API provided by carbon-hadoop and carbon-processing:
-  - Query: integrate carbon-hadoop with engine specific API, like spark data source API 
-  - Data life cycle management: carbon provides utility functions in carbon-processing to manage data life cycle, like data loading, compact, retention, schema evolution. Developer can implement DDLs of their choice and leverage these utility function to do data life cycle management.

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/Carbondata-File-Structure-and-Format.md
----------------------------------------------------------------------
diff --git a/docs/Carbondata-File-Structure-and-Format.md b/docs/Carbondata-File-Structure-and-Format.md
deleted file mode 100644
index fef51eb..0000000
--- a/docs/Carbondata-File-Structure-and-Format.md
+++ /dev/null
@@ -1,55 +0,0 @@
-<!--
-    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.
--->
-
-## Use Case & Motivation :  Why introducing a new file format?
-The motivation behind CarbonData is to create a single file format for all kind of query and analysis on Big Data. Existing data storage formats in Hadoop address only specific use cases requiring users to use multiple file formats for various types of queries resulting in unnecessary duplication of data. 
-
-### Sequential Access / Big Scan
-Such queries select only a few columns with a group by clause but do not contain any filters. This results in full scan over the complete store for the selected columns.  
-![Full Scan Query](/docs/images/format/carbon_data_full_scan.png?raw=true)
-
-### OLAP Style Query / Multi-dimensional Analysis
-These are queries which are typically fired from Interactive Analysis tools. Such queries often select a few columns but involve filters and group by on a column or a grouping expression.  
-![OLAP Scan Query](/docs/images/format/carbon_data_olap_scan.png?raw=true)
-
-
-### Random Access / Narrow Scan
-These are queries used from operational applications and usually select all or most of the columns but do involve a large number of filters which reduce the result to a small size. Such queries generally do not involve any aggregation or group by clause.  
-![Random Scan Query](/docs/images/format/carbon_data_random_scan.png?raw=true)
-
-### Single Format to provide low latency response for all usecases
-The main motivation behind CarbonData is to provide a single storage format for all the usecases of querying big data on Hadoop. Thus CarbonData is able to cover all use-cases into a single storage format.
-![Motivation](/docs/images/format/carbon_data_motivation.png?raw=true)
-
-
-## CarbonData File Structure
-CarbonData file contains groups of data called blocklet, along with all required information like schema, offsets and indices, etc, in a file footer.
-
-The file footer can be read once to build the indices in memory, which can be utilized for optimizing the scans and processing for all subsequent queries.
-
-Each blocklet in the file is further divided into chunks of data called Data Chunks. Each data chunk is organized either in columnar format or row format, and stores the data of either a single column or a set of columns. All blocklets in one file contain the same number and type of Data Chunks.
-
-![Carbon File Structure](/docs/images/format/carbon_data_file_structure_new.png?raw=true)
-
-Each Data Chunk contains multiple groups of data called as Pages. There are three types of pages.
-* Data Page: Contains the encoded data of a column/group of columns.
-* Row ID Page (optional): Contains the row id mappings used when the Data Page is stored as an inverted index.
-* RLE Page (optional): Contains additional metadata used when the Data Page in RLE coded.
-
-![Carbon File Format](/docs/images/format/carbon_data_format_new.png?raw=true)

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/DDL-Operations-on-Carbon.md
----------------------------------------------------------------------
diff --git a/docs/DDL-Operations-on-Carbon.md b/docs/DDL-Operations-on-Carbon.md
deleted file mode 100644
index 07b2be3..0000000
--- a/docs/DDL-Operations-on-Carbon.md
+++ /dev/null
@@ -1,187 +0,0 @@
-<!--
-    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.
--->
-
-* [CREATE TABLE](#CREATE TABLE)
-* [SHOW TABLE](#SHOW TABLE)
-* [DROP TABLE](#DROP TABLE)
-* [COMPACTION](#COMPACTION)
-
-***
-
-
-# CREATE TABLE
-This command can be used to create carbon table by specifying the list of fields along with the table properties.
-
-  ```
-  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
-  ```
-     
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| ---------- |
-| db_name | Name of the Database. Database name should consist of Alphanumeric characters and underscore(_) special character. | YES |
-| field_list | Comma separated List of fields with data type. The field names should consist of Alphanumeric characters and underscore(_) special character.| NO |
-|table_name | The name of the table in Database. Table Name should consist of Alphanumeric characters and underscore(_) special character. | NO |
-| STORED BY | "org.apache.carbondata.format", identifies and creates carbon table. | NO |
-| TBLPROPERTIES | List of carbon table properties. | YES |
-
-### Usage Guideline
-Following are the table properties usage.
-
- - **Dictionary Encoding Configuration**
-
-   By Default dictionary encoding will be enabled for all String columns, and disabled for non-String columns. User can include and exclude columns for dictionary encoding.
-
-  ```ruby
-  TBLPROPERTIES ("DICTIONARY_EXCLUDE"="column1, column2") 
-  TBLPROPERTIES ("DICTIONARY_INCLUDE"="column1, column2") 
-  ```
-Here, DICTIONARY_EXCLUDE will exclude dictionary creation. This is applicable for high-cardinality columns and is a optional parameter. DICTIONARY_INCLUDE will generate dictionary for the columns specified in the list.
-
- - **Row/Column Format Configuration**
-
-   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.
-
-  ```ruby
-  TBLPROPERTIES ("COLUMN_GROUPS"="(column1,column3),(Column4,Column5,Column6)") 
-  ```
- - **Table Block Size Configuration**
-
-   The block size of one table's files on hdfs can be defined using an int value whose size is in MB, the range is form 1MB to 2048MB and the default value is 1024MB, if user didn't define this values in ddl, it would use default value to set.
-
-  ```ruby
-  TBLPROPERTIES ("TABLE_BLOCKSIZE"="512 MB")
-  ```
-Here 512 MB means the block size of this table is 512 MB, user also can set it as 512M or 512.
- - **Inverted Index Configuration**
-
-   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 will be enabled, but user can also set not to use inverted index for some columns.
-
-  ```ruby
-  TBLPROPERTIES ("NO_INVERTED_INDEX"="column1,column3")
-  ```
-Here, NO_INVERTED_INDEX will not use inverted index for the specified columns. This is applicable for high-cardinality columns and is a optional parameter.
-
-*Note : By default all columns except numeric datatype columns are treated as dimensions and all numeric datatype columns are treated as measures. All dimensions except complex datatype columns are part of multi dimensional key(MDK). This behavior can be overridden by using TBLPROPERTIES, If user wants to keep any column (except complex datatype) in multi dimensional key then he can keep the columns either in DICTIONARY_EXCLUDE or DICTIONARY_INCLUDE*
-
-
-**Example:**
-
-  ```
-  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')
-  ```
-***
-
-# SHOW TABLE
-This command can be used to list all the tables in current database or all the tables of a specific database.
-
-  ```ruby
-  SHOW TABLES [IN db_Name];
-  ```
-
-### Parameter Description
-| Parameter | Description | Optional |
-|-----------|-------------| -------- |
-| IN db_Name | Name of the database. Required only if tables of this specific database are to be listed. | YES |
-
-**Example:**
-
-  ```ruby
-  SHOW TABLES IN ProductSchema;
-  ```
-
-***
-
-# DROP TABLE
-This command can be used to delete the existing table.
-
-  ```ruby
-  DROP TABLE [IF EXISTS] [db_name.]table_name;
-  ```
-
-### Parameter Description
-| Parameter | Description | Optional |
-|-----------|-------------| -------- |
-| db_Name | Name of the database. If not specified, current database will be selected. | YES |
-| table_name | Name of the table to be deleted. | NO |
-
-**Example:**
-
-  ```ruby
-  DROP TABLE IF EXISTS productSchema.productSalesTable;
-  ```
-
-***
-
-# COMPACTION
- This command will merge the specified number of segments into one segment. This will enhance the query performance of the table.
-
-  ```ruby
-  ALTER TABLE [db_name.]table_name COMPACT 'MINOR/MAJOR'
-  ```
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| ----------- |
-| db_name | Database name, if it is not specified then it uses current database. | YES |
-| table_name | The name of the table in provided database.| NO |
- 
-### Usage Guideline
-Minor Compaction:
-  In Minor compaction, you can specify number of loads to be merged (compacted). 
-  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.
-   - Level 1: Merging of the segments which are not yet compacted.
-   - Level 2: Merging of the compacted segments again to form a bigger segment.
-
-Major Compaction:
- In Major compaction, many segments can be merged into one big segment. 
- You can specify the compaction size until which the segments will be merged. 
- Major compaction is usually done during the off-peak time.
-
-**Example:**
-
-  ```ruby
-  ALTER TABLE carbontable COMPACT MINOR
-  ALTER TABLE carbontable COMPACT MAJOR
-  ```
-
-***

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/DML-Operations-on-Carbon.md
----------------------------------------------------------------------
diff --git a/docs/DML-Operations-on-Carbon.md b/docs/DML-Operations-on-Carbon.md
deleted file mode 100644
index b910ddb..0000000
--- a/docs/DML-Operations-on-Carbon.md
+++ /dev/null
@@ -1,197 +0,0 @@
-<!--
-    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.
--->
-
-* [LOAD DATA](#LOAD DATA)
-* [SHOW SEGMENTS](#SHOW SEGMENTS)
-* [DELETE SEGMENT BY ID](#DELETE SEGMENT BY ID)
-* [DELETE SEGMENT BY DATE](#DELETE SEGMENT BY DATE)
-
-***
-
-# LOAD DATA
- This command loads the user data in raw format to the Carbon specific data format store, this way Carbon provides good performance while querying the data.Please visit [Data Management](Carbondata-Management.md) for more details on LOAD
-
-### Syntax
-
-  ```ruby
-  LOAD DATA [LOCAL] INPATH 'folder_path' INTO TABLE [db_name.]table_name 
-              OPTIONS(property_name=property_value, ...)
-  ```
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| -------- |
-| folder_path | Path of raw csv data folder or file. | NO |
-| db_name | Database name, if it is not specified then it uses current database. | YES |
-| table_name | The name of the table in provided database.| NO |
-| OPTIONS | Extra options provided to Load | YES |
- 
-
-### Usage Guideline
-Following are the options that can be used in load data:
-- **DELIMITER:** Delimiters can be provided in the load command.
-    
-    ``` ruby
-    OPTIONS('DELIMITER'=',')
-    ```
-- **QUOTECHAR:** Quote Characters can be provided in the load command.
-
-    ```ruby
-    OPTIONS('QUOTECHAR'='"')
-    ```
-- **COMMENTCHAR:** Comment Characters can be provided in the load command if user want to comment lines.
-
-    ```ruby
-    OPTIONS('COMMENTCHAR'='#')
-    ```
-- **FILEHEADER:** Headers can be provided in the LOAD DATA command if headers are missing in the source files.
-
-    ```ruby
-    OPTIONS('FILEHEADER'='column1,column2') 
-    ```
-- **MULTILINE:** CSV with new line character in quotes.
-
-    ```ruby
-    OPTIONS('MULTILINE'='true') 
-    ```
-- **ESCAPECHAR:** Escape char can be provided if user want strict validation of escape character on CSV.
-
-    ```ruby
-    OPTIONS('ESCAPECHAR'='\') 
-    ```
-- **COMPLEX_DELIMITER_LEVEL_1:** Split the complex type data column in a row (eg., a$b$c --> Array = {a,b,c}).
-
-    ```ruby
-    OPTIONS('COMPLEX_DELIMITER_LEVEL_1'='$') 
-    ```
-- **COMPLEX_DELIMITER_LEVEL_2:** Split the complex type nested data column in a row. Applies level_1 delimiter & applies level_2 based on complex data type (eg., a:b$c:d --> Array> = {{a,b},{c,d}}).
-
-    ```ruby
-    OPTIONS('COMPLEX_DELIMITER_LEVEL_2'=':') 
-    ```
-- **ALL_DICTIONARY_PATH:** All dictionary files path.
-
-    ```ruby
-    OPTIONS('ALL_DICTIONARY_PATH'='/opt/alldictionary/data.dictionary')
-    ```
-- **COLUMNDICT:** Dictionary file path for specified column.
-
-    ```ruby
-    OPTIONS('COLUMNDICT'='column1:dictionaryFilePath1, column2:dictionaryFilePath2')
-    ```
-    Note: ALL_DICTIONARY_PATH and COLUMNDICT can't be used together.
-- **DATEFORMAT:** Date format for specified column.
-
-    ```ruby
-    OPTIONS('DATEFORMAT'='column1:dateFormat1, column2:dateFormat2')
-    ```
-    Note: Date formats are specified by date pattern strings. The date pattern letters in Carbon are
-    the same as in JAVA [SimpleDateFormat](http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html).
-
-**Example:**
-
-  ```ruby
-  LOAD DATA local inpath '/opt/rawdata/data.csv' INTO table carbontable
-                         options('DELIMITER'=',', 'QUOTECHAR'='"', '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',
-                                 'DATEFORMAT'='projectjoindate:yyyy-MM-dd'
-                                 )
-  ```
-
-***
-
-# SHOW SEGMENTS
-This command is to show the segments of carbon table to the user.
-
-  ```ruby
-  SHOW SEGMENTS FOR TABLE [db_name.]table_name LIMIT number_of_segments;
-  ```
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| --------- |
-| db_name | Database name, if it is not specified then it uses current database. | YES |
-| table_name | The name of the table in provided database.| NO |
-| number_of_segments | limit the output to this number. | YES |
-
-**Example:**
-
-  ```ruby
-  SHOW SEGMENTS FOR TABLE CarbonDatabase.CarbonTable LIMIT 2;
-  ```
-
-***
-
-# DELETE SEGMENT BY ID
-
-This command is to delete segment by using the segment ID.
-
-  ```ruby
-  DELETE SEGMENT segment_id1,segment_id2 FROM TABLE [db_name.]table_name;
-  ```
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| --------- |
-| segment_id | Segment Id of the load. | NO |
-| db_name | Database name, if it is not specified then it uses current database. | YES |
-| table_name | The name of the table in provided database.| NO |
-
-**Example:**
-
-  ```ruby
-  DELETE SEGMENT 0 FROM TABLE CarbonDatabase.CarbonTable;
-  DELETE SEGMENT 0.1,5,8 FROM TABLE CarbonDatabase.CarbonTable;
-  ```
-  Note: Here 0.1 is compacted segment sequence id.  
-
-***
-
-# DELETE SEGMENT BY DATE
-This command will allow to deletes the Carbon 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.
-
-  ```ruby
-  DELETE SEGMENTS FROM TABLE [db_name.]table_name WHERE STARTTIME BEFORE [DATE_VALUE];
-  ```
-
-### Parameter Description
-
-| Parameter | Description | Optional |
-| ------------- | -----| ------ |
-| DATE_VALUE | Valid segement load start time value. All the segments before this specified date will be deleted. | NO |
-| db_name | Database name, if it is not specified then it uses current database. | YES |
-| table_name | The name of the table in provided database.| NO |
-
-**Example:**
-
-  ```ruby
-  DELETE SEGMENTS FROM TABLE CarbonDatabase.CarbonTable WHERE STARTTIME BEFORE '2017-06-01 12:05:06';  
-  ```
-
-***
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/Data-Management.md
----------------------------------------------------------------------
diff --git a/docs/Data-Management.md b/docs/Data-Management.md
index 72671dc..70f4d28 100644
--- a/docs/Data-Management.md
+++ b/docs/Data-Management.md
@@ -17,143 +17,150 @@
     under the License.
 -->
 
-* [Load Data](#Load Data)
-* [Deleting Data](#Deleting Data)
-* [Compacting Data](#Compacting Data)
-
-
-***
-
-
-# Load Data
-### Scenario
-Once the table is created, data can be loaded into table using LOAD DATA command and will be available for query. When data load is triggered, the data is encoded in Carbon format and copied into HDFS Carbon store path(mentioned in carbon.properties file) in compressed, multi dimentional columnar format for quick analysis queries.
-The same command can be used for loading the 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 as dictionary encoding.
-
-### Procedure
-
-Data loading is a process that involves execution of various steps to read, sort, and encode the date in Carbon store format. Each step will be executed in different threads.
-After data loading process is complete, the status (success/partial success) will be updated to Carbon store metadata. Following are the data load status:
-
-1. Success: All the data is loaded into table and no bad records found.
-2. Partial Success: Data is loaded into table and bad records are found. Bad records are stored at carbon.badrecords.location.
-
-In case of failure, the error will be logged in error log.
-Details of loads can be seen with SHOW SEGMENTS command.
-* Sequence Id
-* Status of data load
-* Load Start time
-* Load End time
-Following steps needs to be performed for invoking data load.
-Run the following command for historical data load:
-```ruby
-LOAD DATA [LOCAL] INPATH 'folder_path' [OVERWRITE] INTO TABLE [db_name.]table_name
-OPTIONS(property_name=property_value, ...)
-```
-OPTIONS are not mandatory for data loading process. Inside OPTIONS user can provide either of any options like DELIMITER,QUOTECHAR, ESCAPERCHAR,MULTILINE as per need.
-
-Note: The path shall be canonical path.
-
-***
-
-# Deleting Data
-### Scenario
-If you have loaded wrong data into the table, or too many bad records and wanted to modify and reload the data, you can delete required loads data. The load can be deleted using the load ID or if the table contains date field then the data can be deleted using the date field.
-
-### Delete by Segment ID
-
-Each segment has a unique segment ID associated with it. Using this segment ID, you can remove the segment.
-Run the following command to get the segmentID.
-```ruby
-SHOW SEGMENTS FOR Table dbname.tablename LIMIT number_of_segments
-```
-Example:
-```ruby
-SHOW SEGMENTS FOR TABLE carbonTable
-```
-The above command will show all the segments of the table carbonTable.
-```ruby
-SHOW SEGMENTS FOR TABLE carbonTable LIMIT 3
-```
-The above DDL will show only limited number of segments specified by number_of_segments.
-
-output: 
-
-| SegmentSequenceId | Status | Load Start Time | Load End Time | 
-|--------------|-----------------|--------------------|--------------------| 
-| 2| Success | 2015-11-19 20:25:... | 2015-11-19 20:49:... | 
-| 1| Marked for Delete | 2015-11-19 19:54:... | 2015-11-19 20:08:... | 
-| 0| Marked for Update | 2015-11-19 19:14:... | 2015-11-19 19:14:... | 
+# Data Management
+This tutorial is going to introduce you to the conceptual details of data management like:
+
+* [Loading Data](#loading-data)
+* [Deleting Data](#deleting-data)
+* [Compacting Data](#compacting-data)
+* [Updating Data](#updating-data)
+
+## Loading Data
+
+* **Scenario**
+
+   After creating a table, you can load data to the table using the [LOAD DATA](dml-operation-on-carbondata.md) 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.
+
+* **Procedure**
+  
+   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.
+   
+   
+| Status | Description |
+|-----------------|------------------------------------------------------------------------------------------------------------|
+| Success | All the data is loaded into table and no bad records found. |
+| Partial Success | Data is loaded into table and bad records are found. Bad records are stored at carbon.badrecords.location. |
+   
+   In case of failure, the error will be logged in error log. Details of loads can be seen with [SHOW SEGMENTS](dml-operation-on-carbondata.md) command. The show segment command output consists of :
+   
+   - SegmentSequenceID
+   - START_TIME OF LOAD
+   - END_TIME OF LOAD 
+   - LOAD STATUS
  
-The show segment command output consists of SegmentSequenceID, START_TIME OF LOAD, END_TIME OF LOAD, and LOAD STATUS. The latest load will be displayed first in the output.
-After you get the segment ID of the segment that you want to delete, execute the following command to delete the selected segment.
-Command:
-```ruby
-DELETE SEGMENT segment_sequence_id1, segments_sequence_id2, .... FROM TABLE tableName
+   The latest load will be displayed first in the output.
+   
+   Refer to [DML operations on CarbonData](dml-operation-on-carbondata.md) for load commands.
+   
+   
+## Deleting Data  
+
+* **Scenario**
+   
+   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.
+   
+* **Procedure** 
+
+   The loaded data can be deleted in the following ways:
+   
+   * Delete by Segment ID
+      
+      After you get the segment ID of the segment that you want to delete, execute the [DELETE](dml-operation-on-carbondata.md ) command for the selected segment.
+      The status of deleted segment is updated to Marked for delete / Marked for Update.
+      
+| SegmentSequenceId | Status            | Load Start Time      | Load End Time        |
+|-------------------|-------------------|----------------------|----------------------|
+| 0                 | Success           | 2015-11-19 19:14:... | 2015-11-19 19:14:... |
+| 1                 | Marked for Update | 2015-11-19 19:54:... | 2015-11-19 20:08:... |
+| 2                 | Marked for Delete | 2015-11-19 20:25:... | 2015-11-19 20:49:... |
+
+   * Delete by Date Field
+   
+      If the table contains date field, you can delete the data based on a specific date.
+
+   * Delete by Record
+
+      To delete records from CarbonData table based on some filter Condition(s).
+      
+      For delete commands refer to [DML operations on CarbonData](dml-operation-on-carbondata.md).
+      
+   * **NOTE**:
+    
+     - 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.
+     
+     - 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.
+     
+     - If the user wants to force delete the segment physically then he can use CLEAN FILES Command.
+        
+Example :
+          
 ```
-Example:
-```ruby
-DELETE SEGMENT l,2,3 FROM TABLE carbonTable
+CLEAN FILES FOR TABLE table1
 ```
 
-### Delete by Date Field
-
-If the table contains date field, you can delete the data based on a specific date.
-Command:
-```ruby
-DELETE FROM TABLE [schema_name.]table_name WHERE[DATE_FIELD]BEFORE [DATE_VALUE]
-```
-Example:
-```ruby
-DELETE FROM TABLE table_name WHERE productionDate BEFORE '2017-07-01'
-```
-Here productionDate is the column of type time stamp.
-The above DDL will delete all the data before the date '2017-07-01'.
+ This DML will physically delete the segment which are "Marked for delete" immediately.
+
+## Compacting Data
+      
+* **Scenario**
+  
+  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.  
+      
+* **Procedure**
+
+  There are two types of compaction Minor and Major compaction.
+  
+  - **Minor Compaction**
+    
+     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.
+     
+     - Level 1: Merging of the segments which are not yet compacted.
+     - Level 2: Merging of the compacted segments again to form a bigger segment. 
+  - **Major Compaction**
+     
+     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. 
+      
+   There are number of parameters related to Compaction that can be set in carbon.properties file 
+   
+| Parameter | Default | Application | Description | Valid Values |
+|-----------------------------------------|---------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|
+| carbon.compaction.level.threshold | 4, 3 | Minor | 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. | NA |
+| carbon.major.compaction.size | 1024 MB | Major | Major compaction size can be configured using this parameter. Sum of the segments which is below this threshold will be merged. | NA |
+| carbon.numberof.preserve.segments | 0 | Minor/Major | 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. | 0-100 |
+| carbon.allowed.compaction.days | 0 | Minor/Major | 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. | 0-100 |
+| carbon.number.of.cores.while.compacting | 2 | Minor/Major | Number of cores which is used to write data during compaction. | 0-100 |   
+  
+   For compaction commands refer to [DDL operations on CarbonData](ddl-operation-on-carbondata.md)
 
+## Updating Data
 
-Note: 
-* 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.
-* 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.
-* If the user wants to force delete the segment physically then he can use CLEAN FILES DML.
-Example:
-```ruby
-CLEAN FILES FOR TABLE table1
-```
-This DML will physically delete the segment which are "Marked for delete" immediately.
+* **Scenario**
 
+    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.
 
+* **Procedure**
 
-***
+    To update we need to specify the column expression with an optional filter condition(s).
 
-# Compacting Data
-### Scenario
-Frequent data ingestion results in several fragmented carbon 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. Carbon provides provision for compacting the loads. Compaction process combines several segments into one large segment by merge sorting the data from across the segments.
+    For update commands refer to [DML operations on CarbonData](dml-operation-on-carbondata.md).
 
-### Prerequisite
 
- The data should be loaded multiple times.
+    
 
-### Procedure
 
-There are two types of compaction Minor and Major compaction.
 
-#### Minor Compaction:
-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.
-* Level 1: Merging of the segments which are not yet compacted.
-* Level 2: Merging of the compacted segments again to form a bigger segment.
-    
-#### Major Compaction:
-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.
-
-### Parameters of Compaction
-| Parameter | Default | Applicable | Description | 
-| --------- | --------| -----------|-------------|
-| carbon.compaction.level.threshold | 4,3 | Minor | 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.
-Valid values are from 0-100. |
-| carbon.major.compaction.size | 1024 mb | Major | Major compaction size can be configured using this parameter. Sum of the segments which is below this threshold will be merged. |
-| carbon.numberof.preserve.segments | 0 | Minor/Major| 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. |
-| carbon.allowed.compaction.days | 0 | Minor/Major| 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. |
-| carbon.number.of.cores.while.compacting | 2 | Minor/Major| Number of cores which is used to write data during compaction. |
+ 
+ 

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/Quick-Start.md
----------------------------------------------------------------------
diff --git a/docs/Quick-Start.md b/docs/Quick-Start.md
deleted file mode 100644
index 0020c71..0000000
--- a/docs/Quick-Start.md
+++ /dev/null
@@ -1,89 +0,0 @@
-<!--
-    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.
--->
-
-# Getting started with Apache CarbonData
-
-This tutorial provides a quick introduction to using CarbonData.
-
-
-## Install
-
-* Download released package of [Spark 1.5.0 or later](http://spark.apache.org/downloads.html)
-* Download and install Apache Thrift 0.9.3, make sure thrift is added to system path.
-* Download [Apache CarbonData code](https://github.com/apache/incubator-carbondata) and build it. Please visit [Building CarbonData And IDE Configuration](Installing-CarbonData-And-IDE-Configuartion.md) for more information.
-
-## Interactive Data Query
-
-### Prerequisite
-Create sample.csv file in carbondata directory
-```
-$ cd carbondata
-$ cat > sample.csv << EOF
-  id,name,city,age
-  1,david,shenzhen,31
-  2,eason,shenzhen,27
-  3,jarry,wuhan,35
-  EOF
-```
-
-### Carbon Spark Shell
-Carbon Spark shell is a wrapper around Apache Spark Shell, it provides a simple way to learn the API, as well as a powerful tool to analyze data interactively. Please visit Apache Spark Documentation for more details on Spark shell.
-Start Spark shell by running the following in the Carbon directory:
-```
-./bin/carbon-spark-shell
-```
-*Note*: In this shell SparkContext is readily available as sc and CarbonContext is available as cc.
-
-**Create table**
-
-```
-scala>cc.sql("create table if not exists test_table (id string, name string, city string, age Int) STORED BY 'carbondata'")
-```
-
-**Load data to table**
-```
-scala>val dataFilePath = new File("../carbondata/sample.csv").getCanonicalPath
-scala>cc.sql(s"load data inpath '$dataFilePath' into table test_table")
-```
-
-**Query data from table**
-
-```
-scala>cc.sql("select * from test_table").show
-scala>cc.sql("select city, avg(age), sum(age) from test_table group by city").show
-```
-
-### Carbon SQL CLI
-The Carbon Spark SQL CLI is a wrapper around Apache Spark SQL CLI. It is a convenient tool to execute queries input from the command line. Please visit Apache Spark Documentation for more information Spark SQL CLI.
-Start the Carbon Spark SQL CLI, run the following in the Carbon directory
-
-```
-./bin/carbon-spark-sql
-```
-And you can provide your own store location by providing configuration using --conf option like:
-```
-./bin/carbon-spark-sql --conf spark.carbon.storepath=/home/root/carbonstore
-```
-
-**Execute Queries in CLI**
-```
-spark-sql> create table if not exists test_table (id string, name string, city string, age Int) STORED BY 'carbondata'
-spark-sql> load data inpath '../sample.csv' into table test_table
-spark-sql> select city, avg(age), sum(age) from test_table group by city
-```

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/configuration-parameters.md
----------------------------------------------------------------------
diff --git a/docs/configuration-parameters.md b/docs/configuration-parameters.md
new file mode 100644
index 0000000..bc6919a
--- /dev/null
+++ b/docs/configuration-parameters.md
@@ -0,0 +1,149 @@
+<!--
+    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.
+-->
+
+# Configuring CarbonData
+ This tutorial guides you through the advanced configurations of CarbonData :
+ 
+ * [System Configuration](#system-configuration)
+ * [Performance Configuration](#performance-configuration)
+ * [Miscellaneous Configuration](#miscellaneous-configuration)
+ * [Spark Configuration](#spark-configuration)
+ 
+ 
+##  System Configuration
+This section provides the details of all the configurations required for the CarbonData System.
+
+<b><p align="center">System Configuration in carbon.properties</p></b>
+
+| Property | Default Value | Description |
+|----------------------------|-------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| carbon.storelocation | /user/hive/warehouse/carbon.store | Location where CarbonData will create the store, and write the data in its own format. NOTE: Store location should be in HDFS. |
+| carbon.ddl.base.hdfs.url | hdfs://hacluster/opt/data | 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. |
+| carbon.badRecords.location | /opt/Carbon/Spark/badrecords | Path where the bad records are stored. |
+| carbon.kettle.home | $SPARK_HOME/carbonlib/carbonplugins | Path used by CarbonData internally to create graph for loading the data. |
+| carbon.data.file.version | 2 | 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. |                    
+
+##  Performance Configuration
+This section provides the details of all the configurations required for CarbonData Performance Optimization.
+
+<b><p align="center">Performance Configuration in carbon.properties</p></b>
+
+* **Data Loading Configuration**
+
+| Parameter | Default Value | Description | Range |
+|--------------------------------------|---------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| carbon.sort.file.buffer.size | 20 | File read buffer size used during sorting. This value is expressed in MB. | Min=1 and Max=100 |
+| carbon.graph.rowset.size | 100000 | Rowset size exchanged between data load graph steps. | Min=500 and Max=1000000 |
+| carbon.number.of.cores.while.loading | 6 | Number of cores to be used while loading data. |  |
+| carbon.sort.size | 500000 | Record count to sort and write intermediate files to temp. |  |
+| carbon.enableXXHash | true | Algorithm for hashmap for hashkey calculation. |  |
+| carbon.number.of.cores.block.sort | 7 | Number of cores to use for block sort while loading data. |  |
+| carbon.max.driver.lru.cache.size | -1 | 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. |  |
+| carbon.max.executor.lru.cache.size | -1 | 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. |  |
+| carbon.merge.sort.prefetch | true | Enable prefetch of data during merge sort while reading data from sort temp files in data loading. |  |
+| carbon.update.persist.enable | true | Enabling this parameter considers persistent data. Enabling this will reduce the execution time of UPDATE operation. |  |
+
+
+
+* **Compaction Configuration**
+  
+| Parameter | Default Value | Description | Range |
+|-----------------------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
+| carbon.number.of.cores.while.compacting | 2 | Number of cores which are used to write data during compaction. |  |
+| carbon.compaction.level.threshold | 4, 3 | 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. | Valid values are from 0-100. |
+| carbon.major.compaction.size | 1024 | 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. |  |
+| carbon.horizontal.compaction.enable | true | 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. |  |
+| carbon.horizontal.UPDATE.compaction.threshold | 1 | 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. | Values between 1 to 10000. |
+| carbon.horizontal.DELETE.compaction.threshold | 1 | 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. | Values between 1 to 10000. |
+
+  
+
+* **Query Configuration**
+  
+| Parameter | Default Value | Description | Range |
+|--------------------------------------|---------------|---------------------------------------------------|---------------------------|
+| carbon.number.of.cores | 4 | Number of cores to be used while querying. |  |
+| carbon.inmemory.record.size | 120000 | Number of records to be in memory while querying. | Min=100000 and Max=240000 |
+| carbon.enable.quick.filter | false | Improves the performance of filter query. |  |
+| no.of.cores.to.load.blocks.in.driver | 10 | Number of core to load the blocks in driver. |  |
+
+
+##   Miscellaneous Configuration
+
+<b><p align="center">Extra Configuration in carbon.properties</p></b>
+
+* **Time format for CarbonData** 
+
+| Parameter | Default Format | Description |
+|-------------------------|---------------------|--------------------------------------------------------------|
+| carbon.timestamp.format | yyyy-MM-dd HH:mm:ss | Timestamp format of input data used for timestamp data type. |
+
+* **Dataload Configuration**
+  
+| Parameter | Default Value | Description |
+|---------------------------------------------|--------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| carbon.sort.file.write.buffer.size | 10485760 | File write buffer size used during sorting. |
+| carbon.lock.type | LOCALLOCK | 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. |
+| carbon.sort.intermediate.files.limit | 20 | Minimum number of intermediate files after which merged sort can be started. |
+| carbon.block.meta.size.reserved.percentage | 10 | Space reserved in percentage for writing block meta data in CarbonData file. |
+| carbon.csv.read.buffersize.byte | 1048576 | csv reading buffer size. |
+| high.cardinality.value | 100000 | To identify and apply compression for non-high cardinality columns. |
+| carbon.merge.sort.reader.thread | 3 | Maximum no of threads used for reading intermediate files for final merging. |
+| carbon.load.metadata.lock.retries | 3 | Maximum number of retries to get the metadata lock for loading data to table. |
+| carbon.load.metadata.lock.retry.timeout.sec | 5 | Interval between the retries to get the lock. |
+| carbon.tempstore.location | /opt/Carbon/TempStoreLoc | Temporary store location. By default it takes System.getProperty("java.io.tmpdir"). |
+| carbon.load.log.counter | 500000 | Data loading records count logger. |   
+
+
+* **Compaction Configuration**
+
+| Parameter | Default Value | Description |
+|-----------------------------------|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| carbon.numberof.preserve.segments | 0 | 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. |
+| carbon.allowed.compaction.days | 0 | 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. |
+| carbon.enable.auto.load.merge | false | To enable compaction while data loading. |
+
+ 
+* **Query Configuration**
+
+| Parameter | Default Value | Description |
+|--------------------------|---------------|-----------------------------------------------------------------------------------------------|
+| max.query.execution.time | 60 | Maximum time allowed for one query to be executed. The value is in minutes. |
+| carbon.enableMinMax | true | Min max is feature added to enhance query performance. To disable this feature, set it false. | 
+  
+* **Global Dictionary Configurations**
+  
+| Parameter | Default Value | Description |
+|---------------------------------------|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| high.cardinality.identify.enable | true | 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 > configured value of high.cardinalityEqually, the value of cardinality is higher than the threshold.value of cardinality/ row number x 100 > configured value of high.cardinality.row.count.percentageEqually, the ratio of the cardinality value to data row number is higher than the configured percentage. |
+| high.cardinality.threshold | 1000000 | Threshold to identify whether high cardinality column.Configuration value formula: Value of cardinality > configured value of high.cardinality. The minimum value is 10000. |
+| high.cardinality.row.count.percentage | 80 | 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 > configured value of high.cardinality.row.count.percentageThe value of the parameter must be larger than 0. |
+| carbon.cutOffTimestamp | 1970-01-01 05:30:00 | 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: The 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. |
+| carbon.timegranularity | SECOND | The property used to set the data granularity level DAY, HOUR, MINUTE, or SECOND. |
+  
+##  Spark Configuration
+ <b><p align="center">Spark Configuration Reference in spark-defaults.conf</p></b>
+ 
+| Parameter | Default Value | Description |
+|----------------------------------------|--------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| spark.driver.memory | 1g | 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. |
+| spark.executor.memory | 1g | Amount of memory to use per executor process. |
+| spark.sql.bigdata.register.analyseRule | org.apache.spark.sql.hive.acl.CarbonAccessControlRules | CarbonAccessControlRules need to be set for enabling Access Control. |
+   
+ 
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata/blob/276a6111/docs/ddl-operation-on-carbondata.md
----------------------------------------------------------------------
diff --git a/docs/ddl-operation-on-carbondata.md b/docs/ddl-operation-on-carbondata.md
new file mode 100644
index 0000000..d261963
--- /dev/null
+++ b/docs/ddl-operation-on-carbondata.md
@@ -0,0 +1,193 @@
+<!--
+    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.
+-->
+
+# DDL Operations on CarbonData
+This tutorial guides you through the data definition language support provided by CarbonData.
+
+## Overview 
+The following DDL operations are supported in CarbonData :
+
+* [CREATE TABLE](#create-table)
+* [SHOW TABLE](#show-table)
+* [DROP TABLE](#drop-table)
+* [COMPACTION](#compaction)
+
+## CREATE TABLE
+  This command can be used to create a CarbonData table by specifying the list of fields along with the table properties.
+  
+```
+   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
+```
+   
+### Parameter Description
+
+| Parameter | Description | Optional |
+|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------|----------|
+| db_name | Name of the database. Database name should consist of alphanumeric characters and underscore(_) special character. | Yes |
+| field_list | Comma separated List of fields with data type. The field names should consist of alphanumeric characters and underscore(_) special character. | No |
+| table_name | The name of the table in Database. Table Name should consist of alphanumeric characters and underscore(_) special character. | No |
+| STORED BY | "org.apache.carbondata.format", identifies and creates a CarbonData table. | No |
+| TBLPROPERTIES | List of CarbonData table properties. |  |
+ 
+ 
+### Usage Guidelines
+            
+   Following are the guidelines for using table properties.
+     
+   - **Dictionary Encoding Configuration**
+   
+       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.
+     
+```
+       TBLPROPERTIES ("DICTIONARY_EXCLUDE"="column1, column2") 
+       TBLPROPERTIES ("DICTIONARY_INCLUDE"="column1, column2") 
+```
+       
+   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.
+     
+   - **Row/Column Format Configuration**
+     
+       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.
+     
+```
+TBLPROPERTIES ("COLUMN_GROUPS"="(column1,column3),
+(Column4,Column5,Column6)") 
+```
+   
+   - **Table Block Size Configuration**
+   
+     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. 
+     
+```
+       TBLPROPERTIES ("TABLE_BLOCKSIZE"="512 MB")
+```
+     
+  Here 512 MB means the block size of this table is 512 MB, you can also set it as 512M or 512.
+   
+   - **Inverted Index Configuration**
+     
+      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.
+     
+```
+       TBLPROPERTIES ("NO_INVERTED_INDEX"="column1,column3")
+```
+
+  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.
+
+   NOTE:
+     
+   - By default all columns other than numeric datatype are treated as dimensions and all columns of numeric datatype are treated as measures. 
+    
+   - 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.
+     
+     
+### Example:
+```
+   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')
+```
+    
+## SHOW TABLE
+
+  This command can be used to list all the tables in current database or all the tables of a specific database.
+```
+  SHOW TABLES [IN db_Name];
+```
+  
+### Parameter Description
+| Parameter  | Description                                                                               | Optional |
+|------------|-------------------------------------------------------------------------------------------|----------|
+| IN db_Name | Name of the database. Required only if tables of this specific database are to be listed. | Yes      |
+
+### Example:
+  
+```
+  SHOW TABLES IN ProductSchema;
+```
+
+## DROP TABLE
+
+ This command is used to delete an existing table.
+
+```
+  DROP TABLE [IF EXISTS] [db_name.]table_name;
+```
+
+### Parameter Description
+| Parameter | Description | Optional |
+|-----------|-------------| -------- |
+| db_Name | Name of the database. If not specified, current database will be selected. | YES |
+| table_name | Name of the table to be deleted. | NO |
+
+### Example:
+
+```
+  DROP TABLE IF EXISTS productSchema.productSalesTable;
+```
+
+## COMPACTION
+
+This command merges the specified number of segments into one segment. This enhances the query performance of the table.
+
+```
+  ALTER TABLE [db_name.]table_name COMPACT 'MINOR/MAJOR';
+```
+  
+  To get details about Compaction refer to [Data Management](data-management.md)
+  
+### Parameter Description
+
+| Parameter | Description | Optional |
+| ------------- | -----| ----------- |
+| db_name | Database name, if it is not specified then it uses current database. | YES |
+| table_name | The name of the table in provided database.| NO |
+
+### Syntax
+
+- **Minor Compaction**
+
+```
+ALTER TABLE table_name COMPACT 'MINOR';
+```
+- **Major Compaction**
+
+```
+ALTER TABLE table_name COMPACT 'MAJOR';
+```
+
+  
+  


Mime
View raw message