-
Notifications
You must be signed in to change notification settings - Fork 82
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
[docs] Document HasVector condition #1386
Conversation
✅ Deploy Preview for condescending-goldwasser-91acf0 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks!
I've confirmed the Rust client snippet, it matches with qdrant/rust-client#208.
For the 'default' vector users should use an empty string (""
). Maybe it's worth to mention that explicitly like we do here: https://qdrant.tech/documentation/concepts/collections/#update-vector-parameters
|
||
|
||
```typescript | ||
client.scroll("{collection_name}", { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked this snippet at qdrant/qdrant-js#91, and it's correct. Thanks, @agourlay!
Rendered
Document new
HasVector
condition released inv1.13.0
.Examples have not been validated against the clients code yet :)