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
cloud_topics/l1: delete an imported segment's tiered-storage objects
When an imported L1 object is removed, delete its backing tiered-storage objects
(the segment, its .tx range manifest, and its .index -- the same set the
archiver would have deleted) so nothing is orphaned.
- delete_objects (abstract_io/file_io/fake_io) takes object_location instead of
object_id, so it routes by the imported location: present -> delete from the
tiered-storage bucket; absent -> delete from the L1 bucket as before.
- Both garbage collectors (metastore and lsm) build the removal list from each
object's imported_ts_location. Native L1 deletion is unchanged.
Testing: an imported-segment GC test (import via add_objects on a migrating
partition, then trim + GC) asserts the backing TS segment is removed, routed by
ts_path; fake_io grows has_ts_segment to observe it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments