-
Notifications
You must be signed in to change notification settings - Fork 2.9k
community[minor]: Create CouchbaseQueryVectorStore #8333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
@ejscribner thanks for your contribution 🎉 are you still interested getting this landed in LangChain? Anything we can do to support? |
|
Thanks for the response! Yes, we definitely will want to land this, but it depends on some other work so I've left it as a draft for now. Hoping to have it ready for review soon 🙂 |
|
3ef56ea to
0a6280e
Compare
0a6280e to
d8118f8
Compare
d8118f8 to
4e7d5b6
Compare
|
Hey @christian-bromann, we're ready to release this now that Couchbase 8.0 is released. I've added docs as well: langchain-ai/docs#1079. Not sure if we need a changeset here or not, but let me know if I need to do anything for that. Thanks for your patience and help with this one! |
|
@ejscribner no problem, thanks for putting this together. Let me check in with the team again and get back to you this week. In the meantime, mind to take a look at this small linting errors? |
…factor existing Couchbase docs (#1079) ## Overview - Adds a new page illustrating usage for new CouchbaseQueryVectorStore (langchain-ai/langchainjs#8333) - Refactors existing page path to ensure distinction between couchbase_search and couchbase_query - Adjusts some language for clarity ## Type of change **Type:** New documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: langchain-ai/langchainjs#8333 <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Lauren Hirata Singh <[email protected]> Co-authored-by: Mason Daugherty <[email protected]>
Fixes # (issue)