Posted by
akashrn5 on
URL: http://apache-carbondata-dev-mailing-list-archive.168.s1.nabble.com/Discussion-Update-feature-enhancement-tp99769p99814.html
Hi david,
Please check below points
One advantage what we get here is , when we insert as new segment, it will
take the new insert flow without converter step and that will be faster.
But here are some points.
1. when you write for new segments for each update, the horizontal
compaction in case of update does not make sense, as it wont happen with
this idea. With this solution, horizontal compaction makes sense only in
delete case.
2. you said we avoid reloading the indexes, but we will avoid reloading the
indexes of complete segment(original segment on which update has happened),
but we still need to reload the index of newly added segment which has
updated right.
3. when you keep on adding multiple segments, we will have more number of
segments and if we does not do compaction, that's one problem and the entry
and size of metadata(table status) increases so much which is another
problem.
So how are you going to handle these cases?
correct me if i'm wrong in my understanding.
Regards,
Akash
--
Sent from:
http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/