Repository navigation
refactor(sdk): internalize legacy data migration - #146
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Scope
list_memories().Changes
import_raw/async_import_raw.import_memory_exact/async_import_memory_exact.get_raw/async_get_rawandlist_raw/async_list_raw.include_rawfromget(); exact lookup returns the actual matched layer (raw_id -> l1_raw, fact ID -> fact layer).list_memories(layers=[\"l1_raw\"]); add generic session/source list filters and include the original source in list/get results. Backend provenance is nowretrieval_sourceinstead of overwritingsourcewithvdb/graph.hy_sdk_migration.py, which directly accesses SDK stores only while Runtime writers are stopped. Semantic migration writes both vector and graph projections.get_write_outcome()public because it is required by the normal durable write queue, not migration.Historical MemHub versions already wrote to the SDK and stored
hy_memory_idmappings, so migration still validates existing records internally. This prevents duplicate raw/memory rows without creating public Client APIs.Verification