Fix Firestore backend keys #46406
Merged
Fix Firestore backend keys #46406
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
fspmarshall
approved these changes
Sep 9, 2024
rosstimothy
added
backport/branch/v14
backport/branch/v15
backport/branch/v16
and removed
backport
labels
GavinFrazar
reviewed
Sep 9, 2024
GavinFrazar
approved these changes
Sep 9, 2024
public-teleport-github-review-bot
bot
removed the request for review
from jakule
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
rosstimothy
force-pushed
the
tross/firestore_keys
branch
from
bab2509
to
601c56c
Compare
|
@rosstimothy See the table below for backport results.
|
rosstimothy
added a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
rosstimothy
added a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
This was referenced Sep 10, 2024
rosstimothy
added a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
rosstimothy
added a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 10, 2024
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow _all_ data which may have been persisted in either format to be retrieved. Fixes #46386
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.
The firestorebk.record field inadvertently was changed from a []byte to a backend.Key. This prevents any existing data which already existed in firestore from being retrieved. This reverts the record key back to []byte and adds a conversion mechanism to allow all data which may have been persisted in either format to be retrieved.
Fixes #46386
changelog: Fixed an issue that prevented the Firestore backend from reading existing data.