I think maintaining a tablestatus backlog file is a good idea. This will
also help us in quick filtering of valid segments as the number of segments
increase during queries execution which involve reading of table status
file.
Show segment DDL can read both the files to display the output.
Dear Jacky,
It was purposefully done like that.the table status need to give the
history of the transactions that happened on the system.This is like an
audit point.
Dear xm_zzc
what is your use case?
In any case we cannot permanently remove the entries from our system.based
on use case we can
Hi
Thank jinzhou started this discussion session.
I also propose to use the proposed solution from manish, not impacts the
current Major and Minor compaction behaviors.
Regards
Liang
manishgupta88 wrote
> Hi,
>
> I agree with @gvramana https://github.com/gvramana;
>
>1. We should *not
