Hi David, Then better we keep a mapping for the segment UUID to virtual segment number in the table status file as well, Any API through which the user can get the segment details should return the virtual segment id instead of the UUID.
On Fri, Sep 4, 2020 at 12:59 PM David CaiQiang <[email protected]> wrote: > Hi Kunal, > > 1. The user uses SQL API or other interfaces. This UUID is a transaction > id, and we already stored the timestamp and other informations in the > segment metadata. > This transaction id can be used in the loading/compaction/update > operation. We can append this id into the log if needed. > Git commit id also uses UUID, so we can consider to use it. What > information do you want to get from the folder name? > > 2. It is easy to fix the show segment command's issue. Maybe we can sort > segment by timestamp and UUID to generate the index id. The user can > continue to use it in other commands. > > > > ----- > Best Regards > David Cai > -- > Sent from: > http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/ >
