You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have old vectordb SDKs in Rust and Javascript. We would like to drop support in favor of the newer lancedb SDKs, so we don't have to maintain two different SDKs.
Part 1: Feature parity
What features do we need in newer SDKs to have parity with old ones?
I had started a somewhat similarly-intentioned list here: #996 However, I think they are slightly different. I added #994 as I think that is the main feature gap between vectordb and lancedb today. Almost all of the examples use embedding functions in some way and so I struggled to switch over the docs and eventually abandoned it for now.
We have old
vectordb
SDKs in Rust and Javascript. We would like to drop support in favor of the newerlancedb
SDKs, so we don't have to maintain two different SDKs.Part 1: Feature parity
What features do we need in newer SDKs to have parity with old ones?
lancedb
Table.add()
should return number of rows writtenmergeInsert
inlancedb
Nodevectordb
in https://github.com/lancedb/lancedb/pull/915/filesTable.indexStats()
inlancedb
lancedb
works in Electron appLow priority:
Part 1.5 Fix important bugs
Table.toArrow
function #1254Part 2: Docs migration
lancedb
Node examples to all docs sectionsPart 3: Cleanup
What do we need to do to wrap up the old SDKs
node
directory from codebase. This will end the release process for that package.vectordb
package from docs. Feature: update docs to use async APIs #1044The text was updated successfully, but these errors were encountered: