-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: stop storing TimelineMetadata in index_part.json as bytes #7699
Draft
koivunej
wants to merge
9
commits into
joonas/legacy_metadata_as_json_in_future
Choose a base branch
from
joonas/no_more_legacy_metadata_format
base: joonas/legacy_metadata_as_json_in_future
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
fix: stop storing TimelineMetadata in index_part.json as bytes #7699
koivunej
wants to merge
9
commits into
joonas/legacy_metadata_as_json_in_future
from
joonas/no_more_legacy_metadata_format
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
no one should be using them anyways. remove the extra test and duplicate wrapping from the test I had missed before.
exposed via TimelineMetadata::with_recalculated_checksum
5 tasks
3024 tests run: 2885 passed, 6 failed, 133 skipped (full report)Failures on Postgres 16Failures on Postgres 15Failures on Postgres 14
Flaky tests (2)Postgres 16
Postgres 15
Test coverage report is not availableThe comment gets automatically updated with the latest test results
48174cd at 2024-05-10T14:15:50.483Z :recycle: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
We've stored metadata as bytes within the
index_part.json
for since long fixed reasons. #7693 added support for reading out normal json serialization of theTimelineMetadata
.Summary of changes
Only write
TimelineMetadata
as json for going forward, keeping the backwards compatibility to reading the metadata as bytes.In documentation and naming, an effort is made to add enough warning signs around TimelineMetadata so that it will receive no changes in the future. We can just add those fields to
IndexPart
directly instead. Changing TimelineMetadata now carries all of the backward compatibility risks without offering any benefits over changingIndexPart
, where we do have a clear strategy (soft json (de)serialization).Builds upon #7693.