Record all possible sizes and handle legacy data migration #13274
+495
−318
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.
What Changed
Core Implementation
requestsSize()
,itemsSize()
,bytesSize()
methods for different size calculationsinternalSize()
to support all sizer types with proper legacy handlinglegacyWriteIndex
field for backward compatibility during migrationLegacy Data Handling
BytesSize
/ItemsSize
historical datalegacyWriteIndex
to track pre-migration items separatelymodernSize + legacySize()
during transition period