[Couchbase VectorStore] Add RecordManager #3397
Conversation
|
would you be able to pull the latest changes since this PR was merged |
JJK801
force-pushed
the
feature/couchbase
branch
2 times, most recently
from
f4ff46a
to
d1f024f
Compare
|
@HenryHengZJ Done |
| options: { | ||
| cleanup: recordManager?.cleanup, | ||
| sourceIdKey: recordManager?.sourceIdKey ?? 'source', | ||
| vectorStoreName: [bucketName, scopeName, collectionName].join('_') |
There was a problem hiding this comment.
@prajwal-pai77 @HenryHengZJ I'm wondering how to handle the vectorStoreName key for indexing, any advice ?
should we include indexName ?
|
Is couchbase supporting record manager from langchainJS? Have you tested it? |
I didn't test it already, but AFAIK the record manager is agnostic of the vector store, its just a DB indexing chunks states. |
Ah okay. I'll test it. There is a reason why record manager is not added to all vector stores. The addvectors and delete methods need to be able to take in ids as parameters in order to be able to use record manager. You can see the example of Qdrant that extends those functions for that |
JJK801
force-pushed
the
feature/couchbase
branch
from
b4d30a2
to
b99cb91
Compare
|
@JJK801 for some reasons i just can't seem to have Couchbase Vector Store working in order to test this, have you got any success with that? |
|
Hi @HenryHengZJ sorry for the delay, i didn't had time to test it and i will finally postpone the usage of couchbase in my project. Feel free to close it if needed. |
|
Closing for now |
Hi Flowise,
This PR adds RecordManager capability to the existing Couchbase vector store node.
Related #3093