Hi David. Thanks for proposing this. *+1 from my side.*
I have seen users with 200K segments table stored in cloud. It will be really slow to reload all the segments where update happened for indexes like SI, min-max, MV. So, it is good to write as a new segment and just load new segment indexes. (try to reuse this flow UpdateTableModel.loadAsNewSegment = true) and user can compact the segments to avoid many new segments created by update. and we can also move the compacted segments to table status history I guess to avoid more entries in table status. Thanks, Ajantha On Fri, Sep 4, 2020 at 1:48 PM David CaiQiang <david.c...@gmail.com> wrote: > Hi Akash, > > 3. Update operation contain a insert operation. Update operation will > do the same thing how the insert operation process this issue. > > > > ----- > Best Regards > David Cai > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ >
