Repository navigation
Add a new field named "version" to the Embeddings model #4438
Description
Overview
This task involves adding a new field named version to the already existing Embeddings model in Studio. This field will be used to track changes between different versions of the embeddings generated by our recommendation models.
Description and outcomes
- Add the
versionfield toEmbeddingsincontentcuration/contentcuration/models.py versionshould be astrwith anulldefault value, and also set as a database index- Run the necessary migration commands
- Add tests that confirm that
versionhas been added correctly
Acceptance Criteria
versionfield is added to theEmbeddingsschema- Tests are written to verify correctness of added field
Assumptions and Dependencies
- This task is dependent on Welcome Embeddings 🚀 #4322
Scope
The scope of this task is limited to;
- Adding the “version” field
- Updating existing schema tests
Accessibility Requirements
NA
Resources
Reacted by Sujai Kumar Gupta
Activity
[-][WIP - DO NOT ASSIGN]: Add "version" field to the Embeddings schema[/-][+][WIP - DO NOT ASSIGN]: Add a new field named "version" to the Embeddings model[/+][-][WIP - DO NOT ASSIGN]: Add a new field named "version" to the Embeddings model[/-][+]Add a new field named "version" to the Embeddings model[/+]thesujai commentedon Apr 17, 2024
Hello @akolson
Implementing this seems straightforward, is this open for community contribution?
bjester commentedon Apr 17, 2024
Hi @thesujai,
Thank you for your interest. This isn't open to community contribution. In fact, we'll most likely close this issue as we pivot the approach soon
thesujai commentedon Apr 17, 2024
Alright no issues. Will find something else to work on
akolson commentedon Apr 14, 2025
Closing this issue as we pivoted the approach