-
Notifications
You must be signed in to change notification settings - Fork 1.2k
feat: Serialization version 2 deprecation notice #5248
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
33 changes: 33 additions & 0 deletions
33
docs/how-to-guides/entity-reserialization-of-from-v2-to-v3.md
This file contains hidden or 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| # Entity Key Re-Serialization from Version 2 to 3 | ||
|
|
||
| Entity Key Serialization version 2 will soon be deprecated, hence we need to shift the serialization and deserilization to version 3. | ||
|
|
||
| But here comes the challegnge where existing FeatuteViews on stores has written features with version 2. A version 2 serialized entity key cant be retrived using version 3 deserilization algorithm. | ||
|
|
||
| ## Reserialize the Feature Views entity Keys to version 3 | ||
|
|
||
| The solution is to reserialize the entity keys from version 2 to version 3. | ||
|
|
||
| Follow the following procedures to reserialize the entity key to version 3 in feature View in an offline / online store. | ||
|
|
||
| In hosrt, you need to iterate through all the feature views in your Feast repository, retrieve their serialized entity keys (if stored in version 2), reserialize them to version 3, and then update the online/offline store or wherever the serialized keys are stored. | ||
|
|
||
| ### 1. Initialize the Feature Store | ||
|
|
||
| Load the FeatureStore object to access all feature views in your repository. | ||
|
|
||
| ### 2. Iterate Through Feature Views | ||
|
|
||
| Use the list_feature_views() method to retrieve all feature views in the repository. | ||
|
|
||
| ### 3. Retrieve Serialized Entity Keys | ||
|
|
||
| For each feature view, retrieve the serialized entity keys stored in the online/offline store or other storage | ||
|
|
||
| ### 4. Reserialize Entity Keys | ||
|
|
||
| Use the reserialize_entity_v2_key_to_v3 function to convert the serialized keys from version 2 to version 3. Use [entity key encoding utils](https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/key_encoding_utils.py) function `reserialize_entity_v2_key_to_v3`. | ||
|
|
||
| ### 5. Update the Online/offline Store | ||
|
|
||
| Write the reserialized keys back to the online/offline store or the appropriate storage |
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not