Skip to content

Support new vector DB implementation in semantic memory - #1406

Merged
sscargal merged 1 commit into
mainfrom
semantic_vector_db
May 20, 2026
Merged

sscargal merged 1 commit into
mainfrom
semantic_vector_db

Conversation

@malatewang

Copy link
Copy Markdown
Contributor

Purpose of the change

Support vector DB for semantic memory

Description

Current semantic memory supports Neo4j and postgres with vector. This PR adds implementation in semantic memory to support the new vector DB and SQL storage.

Fixes/Closes

Fixes #(issue number)

Type of change

[Please delete options that are not relevant.]

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (does not change functionality, e.g., code style improvements, linting)
  • Documentation update
  • Project Maintenance (updates to build scripts, CI, etc., that do not affect the main project)
  • Security (improves security without changing functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

[Please delete options that are not relevant.]

  • Unit Test
  • Integration Test
  • End-to-end Test
  • Test Script (please provide)
  • Manual verification (list step-by-step instructions)

Test Results: [Attach logs, screenshots, or relevant output]

Checklist

[Please delete options that are not relevant.]

  • I have signed the commit(s) within this pull request
  • My code follows the style guidelines of this project (See STYLE_GUIDE.md)
  • I have performed a self-review of my own code
  • I have commented my code
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added unit tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

Maintainer Checklist

  • Confirmed all checks passed
  • Contributor has signed the commit(s)
  • Reviewed the code
  • Run, Tested, and Verified the change(s) work as expected

Screenshots/Gifs

[If applicable, add screenshots or GIFs that show the changes in action. This is especially helpful for API responses. Otherwise, delete this section or type "N/A".]

Further comments

[Add any other relevant information here, such as potential side effects, future considerations, or any specific questions for the reviewer. Otherwise, type "None".]

@malatewang
malatewang force-pushed the semantic_vector_db branch from 8e5f4d0 to 7031681 Compare May 15, 2026 23:50
@sscargal sscargal added this to the v0.4.0 milestone May 16, 2026

@sscargal sscargal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than the Nebula config example changes that should either be reverted to updated for the Nebula Enterprise database, the remaining changes look good to me.

# VectorStore for vector-backed semantic memory.
# Wire it via `semantic_memory.vector_collection`.
semantic_vector_store:
provider: qdrant

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should not use the qdrant database within the Nebular config file; it should be nebula, or left to the Nebula Enterprise team to make the necessary changes..

@edwinyyyu edwinyyyu May 16, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was a bit confused by the existence of this file, and this pattern of one config file per storage backend does not seem to scale. Shouldn't we just comment everything out and rely on user/LLM/script to uncomment anything useful?

@malatewang
malatewang force-pushed the semantic_vector_db branch from 7031681 to 22aee16 Compare May 19, 2026 17:24
@malatewang
malatewang requested a review from sscargal May 19, 2026 17:27

@sscargal sscargal left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks.

@sscargal
sscargal merged commit 7d28ca1 into main May 20, 2026
52 checks passed
@sscargal
sscargal deleted the semantic_vector_db branch May 20, 2026 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants