Comments (1)
Hey, I've taken a look at this and I'd be willing to work on this if the maintainers deem it worthwhile. From what I can see it will require changes in at least the qdrant engine as well as the rust client.
So here's what I understand (at least I think I do, but I'll gladly take hints):
What you showed is the protobuf generated Rust code which comes from the protobuf definitions. The Range
structure is used in the Condition
structure, which is used in the SearchPoints
structure that is passed to the search points
member function of the QdrantClient
. We cannot unilaterally change the layout of the Range
struct because its part of the data that gets passed as a remote procedure call to the qdrant engine. From what I saw in the qdrant engine, there is a conversion layer that converts this range type to segment::types::Range
. This is the type that is actually used by the engine but it also only contains Option<FloatPayloadType>
fields (with FloatPayloadType = f64). So one would have to extend the Fields of this type to be able to hold either i64
or f64
which is definitely possible but will touch a lot of other code.
Hence, I would only want to do this if a maintainer is fine with that. Plus I'd like to know if I missed something and everything is much simpler after all 😁
from rust-client.
Related Issues (20)
- to change QdrantClient fn new from async to just `fn`
- Error type checking HOT 2
- example needs " on_disk:None" | else no compile HOT 1
- Outdated example
- Issues connecting to Qdrant Cloud using client. HOT 2
- Use a more fitting error type HOT 5
- [bug] upsert_points_blocking() api blocks indefinitely without any clear debug message HOT 3
- Grpc-status header missing when using qdrant-cloud: HOT 1
- Better documentation HOT 5
- Any plan to support on the spot text embedding generation like FastEmbed?
- Backward compatibility
- Bug: `update_collection` only accepts `optimizer_config` parameter
- Local Qdrant HOT 2
- How can I get Vec<f32> embedding data from RetrievedPoint? The data of RetrievedPoint type has a "vector_options" of VectorsOptions, but I get no idea to get data from the "vector_options". HOT 1
- Upsert operation is not being performed HOT 4
- Transport Error HOT 2
- Is the QdrantClient thread safe?
- feature request: add seperate function for full-text-search for filters HOT 1
- Semver breakage when updating qdrant-client from 1.3 to 1.7 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rust-client.