carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chenliang...@apache.org
Subject [20/52] [partial] incubator-carbondata-site git commit: updated website version 1
Date Mon, 26 Dec 2016 12:58:40 GMT
http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/docs/overview.md
----------------------------------------------------------------------
diff --git a/content/docs/overview.md b/content/docs/overview.md
deleted file mode 100644
index b3f36ae..0000000
--- a/content/docs/overview.md
+++ /dev/null
@@ -1,177 +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.
--->
-
-![CarbonData_Logo](../docs/images/format/CarbonData_logo.png?raw=true)
-
-This tutorial provides a detailed overview about : 
-
-* CarbonData, 
-* Working and File Format
-* Features
-* Supported Data Types
-* Compatibility
-* Packaging and Interfaces.
-
-##  Introduction
-
-CarbonData(incubating) is a fully indexed columnar and Hadoop native data-store for processing heavy analytical workloads and detailed queries on big data. CarbonData allows  faster interactive query using advanced columnar storage, index, compression and encoding techniques to improve computing efficiency, in turn it will help speedup queries an order of magnitude faster over PetaBytes of data.
- 
-In customer benchmarks, CarbonData has proven to manage Petabyte of data running on extraordinarily low-cost hardware and answers queries around 10 times faster than the current open source solutions (column-oriented SQL on Hadoop data-stores).
-
-Some of the Salient features of CarbonData are :
-* Low-Latency for various types of data access patterns like Sequential,Random and OLAP.
-* Allows fast query on fast data.
-* Ensures Space Efficiency.
-* General format available on Hadoop-ecosystem.
-
-##  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, co-located in HDFS.
-
-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)
-
-##  Features
-
-CarbonData file format is a columnar store in HDFS, it has many features that a modern columnar format has, such as splittable, compression schema ,complex data type etc, and CarbonData has following unique features:
-
-* Stores data along with index: it can significantly accelerate query performance and reduces the I/O scans and CPU resources, where there are filters in the query. CarbonData index consists of multiple level of indices, a processing framework can leverage this index to reduce the task it needs to schedule and process, and it can also do skip scan in more finer grain unit (called blocklet) in task side scanning instead of scanning the whole file.
-* Operable encoded data :Through supporting efficient compression and global encoding schemes, can query on compressed/encoded data, the data can be converted just before returning the results to the users, which is "late materialized".
-* Column group: Allow multiple columns to form a column group that would be stored as row format. This reduces the row reconstruction cost at query time.
-* Supports for various use cases with one single Data format : like interactive OLAP-style query, Sequential Access (big scan), Random Access (narrow scan).
-
-##  Data Types
-
-The following types are supported :
-
-* Numeric Types
-  * SMALLINT 
-  * INT/INTEGER
-  * BIGINT 
-  * DOUBLE
-  * DECIMAL
-
-* Date/Time Types
-  * TIMESTAMP
- 
-* String Types
-  * STRING
-
-* Complex Types
-  * arrays: ARRAY<data_type>
-  * structs: STRUCT<col_name : data_type [COMMENT col_comment], ...>
-  
-##  Compatibility
-
-  
-##  Packaging and Interfaces
-
-###  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.
-
-###  Interfaces
-
-####  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**
-   
-      Carbon has in built 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)
-      ```
-      // 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 who want to integrate carbon into a processing engines like spark,hive or 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-site/blob/b28a17be/content/docs/quick_start.md
----------------------------------------------------------------------
diff --git a/content/docs/quick_start.md b/content/docs/quick_start.md
deleted file mode 100644
index 5540e05..0000000
--- a/content/docs/quick_start.md
+++ /dev/null
@@ -1,140 +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.
--->
-
-![CarbonData_Logo](../docs/images/format/CarbonData_logo.png?raw=true)
-# Quick Start
-This tutorial provides a quick introduction to using CarbonData.
-
-## Getting started with Apache CarbonData
-
-* [Installation](#installation)
-* [Interactive Analysis with Carbon-Spark Shell](#InteractiveAnalysis-with-Carbon-Spark-Shell)
-   * [Basics](#basics)
-   * [Executing Queries](#executing-queries)
-      * [Prerequisites](#prerequisites)
-      * [Create Table](#create-table)
-      * [Load data to Table](#load-data-to-table)
-      * [Query data from table](#query-data-from-table)
-* [Carbon SQL CLI](#carbon-sql-cli)
-   * [Basics](#basics)
-   * [Execute Queries in CLI](#execute-queries-in-cli)
-* [Building CarbonData]()
-
-
-##  Installation
-* Download released package of [Spark 1.5.0 to 1.6.2](http://spark.apache.org/downloads.html)
-* Download and install [Apache Thrift 0.9.3](http://thrift-tutorial.readthedocs.io/en/latest/installation.html), 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 Analysis with 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](http://spark.apache.org/docs/latest/) for more details on Spark shell.
-
-#### Basics
-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.
-
-CarbonData stores and writes the data in its specified format at the default location on the hdfs.
-By default carbon.storelocation is set as :
-```
-hdfs://IP:PORT/Opt/CarbonStore
-```
-And you can provide your own store location by providing configuration using --conf option like:
-```
-./bin/carbon-spark-sql --conf spark.carbon.storepath=<storelocation>
-```
-
-#### Executing Queries
-
-**Prerequisites**
-
-Create sample.csv file in CarbonData directory. The CSV is required for loading data into Carbon.
-```
-$ cd carbondata
-$ cat > sample.csv << EOF
-  id,name,city,age
-  1,david,shenzhen,31
-  2,eason,shenzhen,27
-  3,jarry,wuhan,35
-  EOF
-```
-
-**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](http://spark.apache.org/docs/latest/) for more information Spark SQL CLI.
-
-#### Basics
-Start the Carbon Spark SQL CLI, run the following in the Carbon directory :
-
-```
-./bin/carbon-spark-sql
-```
-CarbonData stores and writes the data in its specified format at the default location on the hdfs.
-By default carbon.storelocation is set as :
-```
-hdfs://IP:PORT/Opt/CarbonStore
-```
-
-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
-```
-## Building CarbonData
-
-To get started, get CarbonData from the [downloads]() on the [http://carbondata.incubator.apache.org.](http://carbondata.incubator.apache.org.)
-CarbonData uses Hadoop’s client libraries for HDFS and YARN and Spark's libraries. Downloads are pre-packaged for a handful of popular Spark versions. 
-
-If you’d like to build CarbonData from source,  Please visit [Building CarbonData And IDE Configuration]()
-
-
-
-
-
-
-
-    
-
-

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/docs/troubleshooting.md
----------------------------------------------------------------------
diff --git a/content/docs/troubleshooting.md b/content/docs/troubleshooting.md
deleted file mode 100644
index d13de95..0000000
--- a/content/docs/troubleshooting.md
+++ /dev/null
@@ -1,32 +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.
--->
-
-# Troubleshooting
-This tutorial is designed to provide troubleshooting for end users and developers 
-who are building, deploying, and using CarbonData.
-
-* ## Prerequisites for Developers
-
-* ## Prerequisites for End Users
-
-* ## General Prevention and Best Practices
-
-* ## Procedure(s)
-
-* ## References

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/docs/use_cases.md
----------------------------------------------------------------------
diff --git a/content/docs/use_cases.md b/content/docs/use_cases.md
deleted file mode 100644
index 87c2381..0000000
--- a/content/docs/use_cases.md
+++ /dev/null
@@ -1,82 +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.
--->
-
-# CarbonData Use Cases
-This tutorial will discuss about the problems that CarbonData address.It shall take you through the identified top use cases of Carbon.
-
-## Introduction
-For big data interactive analysis scenarios, many customers expect sub-second response to query TB-PB level data on general hardware clusters with just a few nodes.
-
-In the current big data ecosystem, there are few columnar storage formats such as ORC and Parquet that are designed for SQL on Big Data. Apache Hive’s ORC format is 
-a columnar storage format with basic indexing capability. However, ORC cannot meet the sub-second query response expectation on TB level data, because ORC format 
-performs only stride level dictionary encoding and all analytical operations such as filtering and aggregation is done on the actual data. Apache Parquet is columnar 
-storage can improve performance in comparison to ORC, because of more efficient storage organization. Though Parquet can provide query response on TB level data in a 
-few seconds, it is still far from the sub-second expectation of interactive analysis users. Cloudera Kudu can effectively solve some query performance issues, but kudu
-is not hadoop native, can’t seamlessly integrate historic HDFS data into new kudu system.
-
-However, CarbonData uses specially engineered optimizations targeted to improve performance of analytical queries which can include filters, aggregation and distinct counts,
-the required data to be stored in an indexed, well organized, read-optimized format, CarbonData’s query performance can achieve sub-second response.
-
-## Motivation: Single Format to provide low latency response for all use cases
-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)
-
-## Use Cases
-* ### Sequential Access
-  - Supports queries that 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.
-  
-  ![Sequential_Scan](../docs/images/format/carbon_data_full_scan.png?raw=true)
-  
-  **Scenario**
-  
-  - ETL jobs
-  - Log Analysis
-    
-* ### Random Access
-  - Supports Point Query. 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.
-    - Row-key query(like HBase)
-    - Narrow Scan
-    - Requires second/sub-second level low latency
-    
-   ![random_access](../docs/images/format/carbon_data_random_scan.png?raw=true)
-    
-  **Scenario**
-    
-    - Operational Query
-    - User Profiling
-    
-* ### Olap Style Query
-  - Supports Interactive data analysis for any dimensions. 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. 
-  It also supports queries that :
-    - involves aggregation/join
-    - Roll-up,Drill-down,Slicing and Dicing
-    - Low-latency ad-hoc query
-    
-   ![Olap_style_query](../docs/images/format/carbon_data_olap_scan.png?raw=true)
-    
-   **Scenario**
-    
-    - Dash-board reporting
-    - Fraud & Ad-hoc Analysis
-    

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/docs/user_guide.md
----------------------------------------------------------------------
diff --git a/content/docs/user_guide.md b/content/docs/user_guide.md
deleted file mode 100644
index 6db4534..0000000
--- a/content/docs/user_guide.md
+++ /dev/null
@@ -1,47 +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.
--->
-![CarbonData_Logo](../docs/images/format/CarbonData_logo.png?raw=true)
-# User Guide
-Welcome to Apache CarbonData. Apache CarbonData(incubating) is a new big data file format for faster interactive query using advanced columnar storage, index, compression and encoding techniques to improve computing efficiency, in turn it will help speedup queries an order of magnitude faster over PetaBytes of data.
-This user guide provides a detailed description about the CarbonData and its features.
-
-Let's get started !
-
-* [Overview]()
-    * [Introduction]()
-    * [Features]()
-    * [Data Types]()
-    * [Compatibility]()
-    * [Packaging and Interfaces]()   
-* [Installing CarbonData]()
-    * [Standalone Spark Cluster]()
-    * [Spark on Yarn Cluster]()
-* [Configuring CarbonData]()
-    * [System Configuration]()
-    * [Performance Configuration]()
-    * [Spark Configuration]()
-* [Using CarbonData]()
-    * [Data Management]()
-    * [DDL Operations]()
-    * [DML Operations]()
-
-
-
-
-

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/configuration.html
----------------------------------------------------------------------
diff --git a/content/documents/configuration.html b/content/documents/configuration.html
deleted file mode 100644
index 275efa8..0000000
--- a/content/documents/configuration.html
+++ /dev/null
@@ -1,441 +0,0 @@
-
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style></style></head><body id="preview">
-<p>&lt;!–<br>
-Licensed to the Apache Software Foundation (ASF) under one<br>
-or more contributor license agreements.  See the NOTICE file<br>
-distributed with this work for additional information<br>
-regarding copyright ownership.  The ASF licenses this file<br>
-to you under the Apache License, Version 2.0 (the<br>
-“License”); you may not use this file except in compliance<br>
-with the License.  You may obtain a copy of the License at</p>
-<pre><code>  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.
-</code></pre>
-<p>–&gt;</p>
-<h1><a id="Configuring_CarbonData_19"></a>Configuring CarbonData</h1>
-<p>This tutorial will guide you through the advance configuration of CarbonData.</p>
-<h2><a id="System_Configuration_22"></a>System Configuration</h2>
-<p>This section provides the details of all the configurations required for Carbon System.<br>
-&lt;b&gt;&lt;p align=“center”&gt;System Configuration in carbon.properties&lt;/p&gt;&lt;/b&gt;</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>carbon.storelocation</td>
-<td>/user/hive/warehouse/carbon.store</td>
-<td>Location where Carbon 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 Carbon 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 to1, then the Carbon supports the data load which is in old format. If the value is set to 2, then the Carbon supports 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>
-<h2><a id="Performance_Configuration_34"></a>Performance Configuration</h2>
-<p>This section provides the details of all the configurations required for Carbon Performance Optimization.<br>
-&lt;b&gt;&lt;p align=“center”&gt;Performance Configuration in carbon.properties&lt;/p&gt;&lt;/b&gt;</p>
-<ol>
-<li><strong>Data Loading Configuration</strong></li>
-</ol>
-<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.</td>
-<td>The value is in MB.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 data loading.</td>
-<td></td>
-</tr>
-<tr>
-<td>carbon.sort.size</td>
-<td>500000</td>
-<td>Record count to sort and write to temp intermediate files.</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 be used for block sort while dataloading.</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.</td>
-<td>The value is in MB. The default value is -1, means there is no memory limit for caching. Only integer values greater than 0 are accepted.</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.</td>
-<td>The value is in MB. The default value is -1, means there is no memory limit for caching. Only integer values greater than 0 are accepted. If this parameter is not configured, then thecarbon.max.driver.lru.cache.size value will be considered.</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>
-<ol start="2">
-<li><strong>Compaction Configuration</strong></li>
-</ol>
-<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 is 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. The value is 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. By default the horizontal compaction is Turned ON but can turn OFF the horizontal compaction by setting the value to false.</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>By default the value is set to 1 and can be altered to 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>By default the value is set to 1 and can be altered to values between 1 to 10000.</td>
-</tr>
-</tbody>
-</table>
-<ol start="3">
-<li><strong>Query Configuration</strong></li>
-</ol>
-<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>
-<h2><a id="Miscellaneous_Configurations_74"></a>Miscellaneous Configurations</h2>
-<p>&lt;b&gt;&lt;p align=“center”&gt;Extra Configuration in carbon.properties&lt;/p&gt;&lt;/b&gt;</p>
-<ol>
-<li><strong>Time format for CarbonData</strong></li>
-</ol>
-<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>
-<ol start="2">
-<li><strong>Dataload Configuration</strong></li>
-</ol>
-<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 Carbon spark application is launched concurrently. - HDFSLOCK: Lock is created on HDFS file system as file. This lock is useful when multiple carbon 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 no of intermediate files after which sort merged to be 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 carbon data 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>
-<ol start="3">
-<li><strong>Compaction Configuration</strong></li>
-</ol>
-<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>
-<ol start="4">
-<li><strong>Query Configuration</strong></li>
-</ol>
-<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>
-<ol start="5">
-<li><strong>Global Dictionary Configurations</strong></li>
-</ol>
-<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.cardinalityThe 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.percentageThe 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: The Carbon 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>
-<h2><a id="Spark_Configuration_125"></a>Spark Configuration</h2>
-<p>&lt;b&gt;&lt;p align=“center”&gt;Spark Configuration Reference in spark-defaults.conf&lt;/p&gt;&lt;/b&gt;</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>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/datamanagemenr.html
----------------------------------------------------------------------
diff --git a/content/documents/datamanagemenr.html b/content/documents/datamanagemenr.html
deleted file mode 100644
index 08d1ecd..0000000
--- a/content/documents/datamanagemenr.html
+++ /dev/null
@@ -1,217 +0,0 @@
-
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style></style></head><body id="preview">
-<p>&lt;!–<br>
-Licensed to the Apache Software Foundation (ASF) under one<br>
-or more contributor license agreements.  See the NOTICE file<br>
-distributed with this work for additional information<br>
-regarding copyright ownership.  The ASF licenses this file<br>
-to you under the Apache License, Version 2.0 (the<br>
-“License”); you may not use this file except in compliance<br>
-with the License.  You may obtain a copy of the License at</p>
-<pre><code>  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.
-</code></pre>
-<p>–&gt;</p>
-<h1><a id="Data_Management_19"></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>
-<h2><a id="Loading_Data_26"></a>Loading Data</h2>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>Once the table is created, data can be loaded into table using <a href="">LOAD DATA</a> command and will be available for query.<br>
-When data load is triggered, the data is encoded in Carbon format and copied into HDFS Carbon store path(specified in carbon.properties file)<br>
-in compressed, multi dimensional columnar format for quick analysis queries. The same command can be used to load new data or to<br>
-update the existing data. Only one data load can be triggered for one table. The high cardinality columns of the dictionary encoding are<br>
-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 date in Carbon store format.<br>
-Each step is executed on different threads. After data loading process is complete, the status (success/partial success) is updated to<br>
-Carbon 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="">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>For load commands refer to <a href="">DML operations on Carbon Data</a></p>
-<p>##Deleting Data</p>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>If you have loaded wrong data into the table, or too many bad records and want to modify and reload the data, you can delete required data loads.<br>
-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 two 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="">DELETE</a> Command for the selected segment.<br>
-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 operations on Carbon Data</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 <a href="">CLEAN FILES</a> Command. This DML will physically delete the segment which are “Marked for delete” immediately.</p>
-</li>
-</ul>
-</li>
-</ul>
-<p>##Compacting Data</p>
-<ul>
-<li>
-<p><strong>Scenario</strong></p>
-<p>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<br>
-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,<br>
-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.</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<br>
-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>Thisproperty 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 <a href="http://compaction.No">compaction.No</a> 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 operations on Carbon Data</a></p>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/ddl.html
----------------------------------------------------------------------
diff --git a/content/documents/ddl.html b/content/documents/ddl.html
deleted file mode 100644
index 90af0eb..0000000
--- a/content/documents/ddl.html
+++ /dev/null
@@ -1,227 +0,0 @@
-
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style></style></head><body id="preview">
-<p>&lt;!–<br>
-Licensed to the Apache Software Foundation (ASF) under one<br>
-or more contributor license agreements.  See the NOTICE file<br>
-distributed with this work for additional information<br>
-regarding copyright ownership.  The ASF licenses this file<br>
-to you under the Apache License, Version 2.0 (the<br>
-“License”); you may not use this file except in compliance<br>
-with the License.  You may obtain a copy of the License at</p>
-<pre><code>  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.
-</code></pre>
-<p>–&gt;</p>
-<h1><a id="DDL_Operations_on_CarbonData_19"></a>DDL Operations on CarbonData</h1>
-<p>This tutorial will guide you through the data definition language support provided by CarbonData.</p>
-<h2><a id="Overview_22"></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>
-<h2><a id="CREATE_TABLE_30"></a>CREATE TABLE</h2>
-<p>This command can be used to create carbon 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_40"></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 carbon table.</td>
-<td>No</td>
-</tr>
-<tr>
-<td>TBLPROPERTIES</td>
-<td>List of carbon table properties.</td>
-<td></td>
-</tr>
-</tbody>
-</table>
-<h3><a id="Usage_Guideline_50"></a>Usage Guideline</h3>
-<p>Following are the table properties usage.</p>
-<ul>
-<li>
-<p><strong>Dictionary Encoding Configuration</strong></p>
-<p>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.</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 set to 1024MB and supports a range of 1MB to 2048MB.<br>
-If the user does’nt 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, user also can 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_96"></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>
-<h2><a id="SHOW_TABLE_114"></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_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>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_126"></a>Example:</h3>
-<pre><code>SHOW TABLES IN ProductSchema;
-</code></pre>
-<h2><a id="DROP_TABLE_132"></a>DROP TABLE</h2>
-<p>This command can be used to delete the existing table.</p>
-<pre><code>DROP TABLE [IF EXISTS] [db_name.]table_name;
-</code></pre>
-<h3><a id="Parameter_Description_140"></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_146"></a>Example:</h3>
-<pre><code>DROP TABLE IF EXISTS productSchema.productSalesTable;
-</code></pre>
-<h2><a id="COMPACTION_152"></a>COMPACTION</h2>
-<p>This command will merge the specified number of segments into one segment. This will enhance 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</a></p>
-<h3><a id="Parameter_Description_162"></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_169"></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>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/dml.html
----------------------------------------------------------------------
diff --git a/content/documents/dml.html b/content/documents/dml.html
deleted file mode 100644
index b89b982..0000000
--- a/content/documents/dml.html
+++ /dev/null
@@ -1,258 +0,0 @@
-
-<!DOCTYPE html><html><head><meta charset="utf-8"><title>Untitled Document.md</title><style></style></head><body id="preview">
-<p>&lt;!–<br>
-Licensed to the Apache Software Foundation (ASF) under one<br>
-or more contributor license agreements.  See the NOTICE file<br>
-distributed with this work for additional information<br>
-regarding copyright ownership.  The ASF licenses this file<br>
-to you under the Apache License, Version 2.0 (the<br>
-“License”); you may not use this file except in compliance<br>
-with the License.  You may obtain a copy of the License at</p>
-<pre><code>  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.
-</code></pre>
-<p>–&gt;</p>
-<h1><a id="DML_Operations_on_CarbonData_19"></a>DML Operations on CarbonData</h1>
-<p>This tutorial will guide you through the data manipulation language support provided by CarbonData.</p>
-<h2><a id="Overview_22"></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-segements">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>
-<h2><a id="LOAD_DATA_30"></a>LOAD DATA</h2>
-<p>This command loads the user data in raw format to the Carbon specific data format store, this allows Carbon to provides good performance while querying the data.<br>
-Please visit <a href="">Data Management</a> for more details on LOAD.</p>
-<h3><a id="Syntax_35"></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_45"></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_55"></a>Usage Guideline</h3>
-<p>Following are the options that can be used for loading 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 Carbon 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_119"></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>
-<h2><a id="SHOW_SEGMENTS_136"></a>SHOW SEGMENTS</h2>
-<p>This command is used to get the segments of carbon table.</p>
-<pre><code>SHOW SEGMENTS FOR TABLE [db_name.]table_name LIMIT number_of_segments;
-</code></pre>
-<h3><a id="Parameter_Description_144"></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_152"></a>Example:</h3>
-<pre><code>SHOW SEGMENTS FOR TABLE CarbonDatabase.CarbonTable LIMIT 4;
-</code></pre>
-<h2><a id="DELETE_SEGMENT_BY_ID_157"></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.<br>
-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_171"></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_178"></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>
-<h2><a id="DELETE_SEGMENT_BY_DATE_185"></a>DELETE SEGMENT BY DATE</h2>
-<p>This command will allow to delete the Carbon segment(s) from the store based on the date provided by the user in the DML command.<br>
-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_194"></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_202"></a>Example:</h3>
-<pre><code>DELETE SEGMENTS FROM TABLE CarbonDatabase.CarbonTable WHERE STARTTIME BEFORE '2017-06-01 12:05:06';  
-</code></pre>
-
-</body></html>

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/CarbonData_logo.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/CarbonData_logo.png b/content/documents/images/format/CarbonData_logo.png
deleted file mode 100644
index bc09b23..0000000
Binary files a/content/documents/images/format/CarbonData_logo.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_file_structure_new.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_file_structure_new.png b/content/documents/images/format/carbon_data_file_structure_new.png
deleted file mode 100644
index 3f9241b..0000000
Binary files a/content/documents/images/format/carbon_data_file_structure_new.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_format_new.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_format_new.png b/content/documents/images/format/carbon_data_format_new.png
deleted file mode 100644
index 9d0b194..0000000
Binary files a/content/documents/images/format/carbon_data_format_new.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_full_scan.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_full_scan.png b/content/documents/images/format/carbon_data_full_scan.png
deleted file mode 100644
index 46715e7..0000000
Binary files a/content/documents/images/format/carbon_data_full_scan.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_motivation.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_motivation.png b/content/documents/images/format/carbon_data_motivation.png
deleted file mode 100644
index 6e454c6..0000000
Binary files a/content/documents/images/format/carbon_data_motivation.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_olap_scan.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_olap_scan.png b/content/documents/images/format/carbon_data_olap_scan.png
deleted file mode 100644
index c1dfb18..0000000
Binary files a/content/documents/images/format/carbon_data_olap_scan.png and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/b28a17be/content/documents/images/format/carbon_data_random_scan.png
----------------------------------------------------------------------
diff --git a/content/documents/images/format/carbon_data_random_scan.png b/content/documents/images/format/carbon_data_random_scan.png
deleted file mode 100644
index 7d44d34..0000000
Binary files a/content/documents/images/format/carbon_data_random_scan.png and /dev/null differ


Mime
View raw message