Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #1766] [MERGED] [CHORE] Migration from vectordb to @lancedb/lancedb NodeJS SDK #3774

New Issue
Closed
opened 2026-02-22 18:34:28 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:34:28 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/1766
Author: @timothycarambat
Created: 6/27/2024
Status: ✅ Merged
Merged: 6/27/2024
Merged by: @timothycarambat

Base: master ← Head: migrate-to-new-lancedb

📝 Commits (2)

  • 0764058 WIP on migration to @lancedb/lancedb NodeJS SDK
  • d3139d2 Merge branch 'master' of github.com:Mintplex-Labs/anything-llm into migrate-to-new-lancedb

📊 Changes

3 files changed (+148 additions, -121 deletions)

View changed files

📝 server/package.json (+1 -1)
📝 server/utils/vectorDbProviders/lance/index.js (+51 -12)
📝 server/yarn.lock (+96 -108)

📄 Description

Migrate support for LanceDB from their old vectordb library to their new @lancedb/lancedb package.
This bumps our version to the latest, but also comes with some API changes.

Tests:

  • Search/CRUD post-update on old vectordb created collections
  • Search/CRUD on newly created collections with new implementation

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/1766 **Author:** [@timothycarambat](https://github.com/timothycarambat) **Created:** 6/27/2024 **Status:** ✅ Merged **Merged:** 6/27/2024 **Merged by:** [@timothycarambat](https://github.com/timothycarambat) **Base:** `master` ← **Head:** `migrate-to-new-lancedb` --- ### 📝 Commits (2) - [`0764058`](https://github.com/Mintplex-Labs/anything-llm/commit/0764058b284593e2ba33ae88dfb17cf1028a6df4) WIP on migration to @lancedb/lancedb NodeJS SDK - [`d3139d2`](https://github.com/Mintplex-Labs/anything-llm/commit/d3139d201b34f6f8e6b5a4741d7114c6f8f55e19) Merge branch 'master' of github.com:Mintplex-Labs/anything-llm into migrate-to-new-lancedb ### 📊 Changes **3 files changed** (+148 additions, -121 deletions) <details> <summary>View changed files</summary> 📝 `server/package.json` (+1 -1) 📝 `server/utils/vectorDbProviders/lance/index.js` (+51 -12) 📝 `server/yarn.lock` (+96 -108) </details> ### 📄 Description Migrate support for LanceDB from their old `vectordb` library to their new `@lancedb/lancedb` package. This bumps our version to the latest, but also comes with some API changes. Tests: - Search/CRUD post-update on old `vectordb` created collections - Search/CRUD on newly created collections with new implementation --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:34:28 -05:00
yindo closed this issue 2026-02-22 18:34:28 -05:00
yindo changed title from [PR #1766] [CHORE] Migration from `vectordb` to @lancedb/lancedb NodeJS SDK to [PR #1766] [MERGED] [CHORE] Migration from `vectordb` to @lancedb/lancedb NodeJS SDK 2026-06-05 15:15:08 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3774
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?