fix: serialize distinct cache in catalog #25990
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The distinct cache info for tables was not serialized in the catalog. This fixes that, but also updates the catalog serialization to use the same snapshot pattern for serialization from the Catalog type all the way down. This removes the need to serialize the
db_map
from the catalog.The Eq and PartialEq derives were removed from Catalog and InnerCatalog as they were only used in tests, where assertions using them were replaced by insta snapshot tests.
A test was added to check serialization/deserialization of distinct caches in the catalog.
There is no issue for this.