feat: integrate vikingdb-python-sdk for memory backend#349
Merged
yaozheng-fang merged 4 commits intovolcengine:mainfrom Dec 11, 2025
Merged
feat: integrate vikingdb-python-sdk for memory backend#349yaozheng-fang merged 4 commits intovolcengine:mainfrom
yaozheng-fang merged 4 commits intovolcengine:mainfrom
Conversation
ethfoo
force-pushed
the
feat/viking-memory-sdk
branch
from
9942746 to
8322e25
Compare
yaozheng-fang
approved these changes
Dec 11, 2025
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
2 participants
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.
This PR integrates the official vikingdb-python-sdk into the VeADK memory backend system, replacing the previous custom implementation with the official SDK client.
Changes
• Dependencies: Added vikingdb-python-sdk>=0.1.3 to pyproject.toml
• Memory Backend: Updated VikingDBLTMBackend to use the official SDK client (VikingMem) instead of custom implementation
• API Updates:
• Replaced custom add_messages method with SDK's add_session method
• Updated search_memory to use SDK's native implementation
• Added _get_sdk_client() method for proper SDK client initialization
• Code Cleanup: Removed deprecated memory operation methods from ve_viking_db_memory.py
Benefits
• Official Support: Uses the officially maintained VikingDB Python SDK
• Better Reliability: Leverages tested and maintained SDK methods
• Future Compatibility: Ensures compatibility with future VikingDB API updates
• Simplified Maintenance: Reduces custom code maintenance overhead
Testing
The changes maintain the same interface for memory operations while using the underlying SDK. All existing functionality for saving and searching memories remains intact.