Hi dhatchayani,

please find the comments below 

1. Yes you are right, design document contains this, in datamap status file
we will add the mapping of synchrinization of main table and datamap, based
on that incremental load is done.
2. I will tell in general, if main table has 10 segments, and then you do
lazy load, then first segment of datamap is created with 10segments data,
after that 2 loads are done to main table, then for next lazy load, only two
segments data of main table are loaded to second segment of datamap. For
preaggregate we will keep same behavior as old. 

3. Currently also, if you consider the MV datamap, it supports only lazy
load. So when the main table data and the datamap data are not synced then
the datamao is not selected for pruning, and everytime to decide this, we
read the datamap  status file and make the plan. So no issues in the reading
status.

I  hope i cleared your doubts, if any more doubts or suggestions, please get
back

Thank you



--
Sent from: 
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/

Reply via email to