You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new API named DB::OpenAndTrimHistory is added to imported by (#9223). This API will open DB and trim data to the timestamp specified by trim_ts (The data with newer timestamp than specified trim bound will be removed). Currently this API will iterate every sst file to trim data which has newer timestamp than specified trim_ts. Actually files with max_ts smaller than trim_ts should be safe and no need to be iterated.
Since we can track sst file's max and min timestamp according (#8959),
I think the OpenAndTrimHistory API can be optimized by skipping unnessary sst files with call API CompactFiles instead of CompactRangeInternal.
A new API named DB::OpenAndTrimHistory is added to imported by (#9223). This API will open DB and trim data to the timestamp specified by trim_ts (The data with newer timestamp than specified trim bound will be removed). Currently this API will iterate every sst file to trim data which has newer timestamp than specified trim_ts. Actually files with max_ts smaller than trim_ts should be safe and no need to be iterated.
Since we can track sst file's max and min timestamp according (#8959),
I think the OpenAndTrimHistory API can be optimized by skipping unnessary sst files with call API CompactFiles instead of CompactRangeInternal.
@riversand963
The text was updated successfully, but these errors were encountered: