Hi Cao Lu,
  I suggest to mention the following information.

1. table creation
modify schema.thrift, add optional partitioner information to TableSchema

2. alter table add/drop partition

3. data loading of partition table
use  partitioner information of TableSchema to generate the table
partitioner, then use this partitioner to repartition input RDD, finally
reuse loadDataFrame flow.

use partition id to replace task no in carbondata/inde file name, so no need
to store partition information in footer and index file, 

4. detail query on partition table with partition column filter.
use partition column filter to get partition id list, use partition id list
to filter BTree.

5. partition tables join on partition column




--
View this message in context: 
http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/Discussion-Implement-Partition-Table-Feature-tp10938p11139.html
Sent from the Apache CarbonData Mailing List archive mailing list archive at 
Nabble.com.

Reply via email to