Skip to content

[Backport] Skip tombstone segment refresh in metadata cache#17080

Closed
findingrish wants to merge 5 commits intoapache:31.0.0from
findingrish:backport_17025_1
Closed

[Backport] Skip tombstone segment refresh in metadata cache#17080
findingrish wants to merge 5 commits intoapache:31.0.0from
findingrish:backport_17025_1

Conversation

@findingrish
Copy link
Copy Markdown
Contributor

Backport #17025 to 31.0.0.

* Skip refresh for unused segments in metadata cache

* Cover the condition where a used segment missing schema is marked for refresh

* Fix test
This PR apache#16890 introduced a change to skip adding tombstone segments to the cache.
It turns out that as a side effect tombstone segments appear unavailable in the console. This happens because availability of a segment in Broker is determined from the metadata cache.

The fix is to keep the segment in the metadata cache but skip them from refresh.

This doesn't affect any functionality as metadata query for tombstone returns empty causing continuous refresh of those segments.
@findingrish findingrish changed the base branch from master to 31.0.0 September 16, 2024 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant