carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From chenliang...@apache.org
Subject [26/54] [partial] incubator-carbondata-site git commit: updated website for release
Date Tue, 20 Dec 2016 02:26:02 GMT
http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/0bb92d4d/src/main/webapp/docs/data_management.md
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/data_management.md b/src/main/webapp/docs/data_management.md
deleted file mode 100755
index f56b577..0000000
--- a/src/main/webapp/docs/data_management.md
+++ /dev/null
@@ -1,135 +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.
--->
-
-# 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)
-
-## Loading 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(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 date in Carbon store format.
-   Each step is executed on different threads. After data loading process is complete, the
status (success/partial success) is updated to 
-   Carbon 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]() command. The show segment command output consists of :
-   
-   - SegmentSequenceID
-   - START_TIME OF LOAD
-   - END_TIME OF LOAD 
-   - LOAD STATUS
- 
-   The latest load will be displayed first in the output.
-   
-   For load commands refer to [DML operations on Carbon Data]()
-   
-##Deleting Data  
-
-* **Scenario**
-   
-   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. 
-   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.
-   
-* **Procedure** 
-
-   The loaded data can be deleted in the following two ways :
-   1. Delete by Segment ID
-     
-      After you get the segment ID of the segment that you want to delete, execute the [DELETE]()
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:...
|
-
-   2. Delete by Date Field
-   
-      If the table contains date field, you can delete the data based on a specific date.
-      
-      For delete commands refer to [DML operations on Carbon 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]()
Command. This DML will physically delete the segment which are "Marked for delete" immediately.
-   
-   
-##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.  
-      
-* **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 | 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. | 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 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. | 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 Carbon Data]()
-    
-
-
-
-
- 
- 

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/0bb92d4d/src/main/webapp/docs/ddl.md
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/ddl.md b/src/main/webapp/docs/ddl.md
deleted file mode 100755
index eafb257..0000000
--- a/src/main/webapp/docs/ddl.md
+++ /dev/null
@@ -1,184 +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.
--->
-
-# DDL Operations on CarbonData
-This tutorial will guide 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 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. |  |
- 
-### 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 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.
-     
-       ```ruby
-       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 set to 1024MB and supports a range of
1MB to 2048MB.
-        If the user does'nt 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, 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 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 can be used to delete the 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 will merge the specified number of segments into one segment. This will enhance
the query performance of the table.
-
-  ```
-  ALTER TABLE [db_name.]table_name COMPACT 'MINOR/MAJOR';
-  ```
-  
-  To get details about Compaction refer to [Data Management]()
-  
-### 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 carbontable COMPACT MINOR;
-```
-- **Major Compaction**
-
-```
-ALTER TABLE carbontable COMPACT MAJOR;
-```
-
-  
-  

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/0bb92d4d/src/main/webapp/docs/dml.md
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/dml.md b/src/main/webapp/docs/dml.md
deleted file mode 100755
index 8ab277c..0000000
--- a/src/main/webapp/docs/dml.md
+++ /dev/null
@@ -1,207 +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.
--->
-
-# DML Operations on CarbonData
-This tutorial will guide you through the data manipulation language support provided by CarbonData.
-
-## Overview 
-The following DML operations are supported in CarbonData :
-
-* [LOAD DATA](#load-data)
-* [SHOW SEGMENTS](#show-segements)
-* [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 allows Carbon to provides good performance while querying the data.
-Please visit [Data Management]() for more details on LOAD.
-
-### Syntax
-
-```
-LOAD DATA [LOCAL] INPATH 'folder_path' 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, ESCAPECHAR,MULTILINE as per requirement.
-
-Note: The path shall be canonical path.
-
-### 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 for loading data:
-- **DELIMITER:** Delimiters can be provided in the load command.
-    
-    ``` 
-    OPTIONS('DELIMITER'=',')
-    ```
-- **QUOTECHAR:** Quote Characters can be provided in the load command.
-
-    ```
-    OPTIONS('QUOTECHAR'='"')
-    ```
-- **COMMENTCHAR:** Comment Characters can be provided in the load command if user want to
comment lines.
-
-    ```
-    OPTIONS('COMMENTCHAR'='#')
-    ```
-- **FILEHEADER:** Headers can be provided in the LOAD DATA command if headers are missing
in the source files.
-
-    ```
-    OPTIONS('FILEHEADER'='column1,column2') 
-    ```
-- **MULTILINE:** CSV with new line character in quotes.
-
-    ```
-    OPTIONS('MULTILINE'='true') 
-    ```
-- **ESCAPECHAR:** Escape char can be provided if user want strict validation of escape character
on CSV.
-
-    ```
-    OPTIONS('ESCAPECHAR'='\') 
-    ```
-- **COMPLEX_DELIMITER_LEVEL_1:** Split the complex type data column in a row (eg., a$b$c
--> Array = {a,b,c}).
-
-    ```
-    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}}).
-
-    ```
-    OPTIONS('COMPLEX_DELIMITER_LEVEL_2'=':') 
-    ```
-- **ALL_DICTIONARY_PATH:** All dictionary files path.
-
-    ```
-    OPTIONS('ALL_DICTIONARY_PATH'='/opt/alldictionary/data.dictionary')
-    ```
-- **COLUMNDICT:** Dictionary file path for specified column.
-
-    ```
-    OPTIONS('COLUMNDICT'='column1:dictionaryFilePath1, column2:dictionaryFilePath2')
-    ```
-    Note: ALL_DICTIONARY_PATH and COLUMNDICT can't be used together.
-    
-- **DATEFORMAT:** Date format for specified column.
-
-    ```
-    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. Refer to [SimpleDateFormat](http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html).
-
-
-### Example:
-
-```
-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'
-                                 )
-
-```
-
-## SHOW SEGMENTS
-
-This command is used to get the segments of carbon table.
-
-```
-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:
-```
-SHOW SEGMENTS FOR TABLE CarbonDatabase.CarbonTable LIMIT 4;
-```
-
-## DELETE SEGMENT BY ID
-
-This command is used to delete segment by using the segment ID. Each segment has a unique
segment ID associated with it. 
-Using this segment ID, you can remove the segment.
-
-The following command will get the segmentID.
-```
-SHOW SEGMENTS FOR Table dbname.tablename LIMIT number_of_segments
-```
-After you retrieve the segment ID of the segment that you want to delete, execute the following
command to delete the selected segment.
-```
-DELETE SEGMENT segment_sequence_id1, segments_sequence_id2, .... FROM TABLE tableName
-```
-
-### 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:
-```
-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 delete 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.
-
-```
-DELETE FROM TABLE [schema_name.]table_name WHERE[DATE_FIELD]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:
-
- ```
- 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-site/blob/0bb92d4d/src/main/webapp/docs/faq.md
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/faq.md b/src/main/webapp/docs/faq.md
deleted file mode 100755
index 51f85bc..0000000
--- a/src/main/webapp/docs/faq.md
+++ /dev/null
@@ -1,18 +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.
--->
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/0bb92d4d/src/main/webapp/docs/fonts/FontAwesome.otf
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/fonts/FontAwesome.otf b/src/main/webapp/docs/fonts/FontAwesome.otf
deleted file mode 100644
index 401ec0f..0000000
Binary files a/src/main/webapp/docs/fonts/FontAwesome.otf and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-carbondata-site/blob/0bb92d4d/src/main/webapp/docs/fonts/OpenSans-Bold.eot
----------------------------------------------------------------------
diff --git a/src/main/webapp/docs/fonts/OpenSans-Bold.eot b/src/main/webapp/docs/fonts/OpenSans-Bold.eot
deleted file mode 100644
index 016123b..0000000
Binary files a/src/main/webapp/docs/fonts/OpenSans-Bold.eot and /dev/null differ


Mime
View raw message