carbondata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [2/4] incubator-carbondata git commit: Corrected image path
Date Wed, 29 Jun 2016 13:05:06 GMT
Corrected image path


Branch: refs/heads/master
Commit: 0963f8389feed68302d5e70acbd9b7ce07ef9be7
Parents: 5d19fc0
Author: ravipesala <>
Authored: Wed Jun 29 18:20:44 2016 +0530
Committer: ravipesala <>
Committed: Wed Jun 29 18:20:44 2016 +0530

 docs/ | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/docs/ b/docs/
index e5d97b8..d1d4971 100644
--- a/docs/
+++ b/docs/
@@ -3,20 +3,20 @@ The motivation behind CarbonData is to create a single file format for all
 ### Sequential Access / Big Scan
 Such queries select only a few columns with a group by clause but do not contain any filters.
This results in full scan over the complete store for the selected columns.  
-[[/images/format/carbon_data_full_scan.png|Full Scan Query]]
+![Full Scan Query](/docs/images/format/carbon_data_full_scan.png?raw=true)
 ### OLAP Style Query / Multi-dimensional Analysis
 These are queries which are typically fired from Interactive Analysis tools. Such queries
often select a few columns but involve filters and group by on a column or a grouping expression.

-[[/images/format/carbon_data_olap_scan.png|OLAP Scan Query]]
+![OLAP Scan Query](/docs/images/format/carbon_data_olap_scan.png?raw=true)
 ### Random Access / Narrow Scan
 These are queries used from operational applications and usually select all or most of the
columns but do involve a large number of filters which reduce the result to a small size.
Such queries generally do not involve any aggregation or group by clause.  
-[[/images/format/carbon_data_random_scan.png|Random Scan Query]]
+![Random Scan Query](/docs/images/format/carbon_data_random_scan.png?raw=true)
 ### Single Format to provide low latency response for all usecases
 The main motivation behind CarbonData is to provide a single storage format for all the usecases
of querying big data on Hadoop. Thus CarbonData is able to cover all use-cases into a single
storage format.
 ## CarbonData File Structure
@@ -26,11 +26,11 @@ The file footer can be read once to build the indices in memory, which
can be ut
 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.
-[[/images/format/carbon_data_file_structure_new.png|Carbon File Structure]]
+![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
 * 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.
-[[/images/format/carbon_data_format_new.png|Carbon File Format]]
+![Carbon File Format](/docs/images/format/carbon_data_format_new.png?raw=true)

View raw message