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
In case of future updates and features from Qdrant, we should increase the adaptability of our library. With this proposed change, as soon as Qdrant introduces new features, users of this library can instantly integrate and utilize them without having to wait for explicit support in this package.
I'm suggesting two potential paths:
Direct Implementation in Qdrant Client: We can add an executeRaw function to the main Qdrant client class. Here's a draft of that function:
However, this approach does introduce some code redundancy.
Utilize AbstractEndpoint: Instead of direct implementation, we can modify the createRequest method in AbstractEndpoint to be public and static. This way, we centralize the request creation process.
Hello @gregpriday, thank you for sharing your opinion. Let's discuss this matter again to determine whether it is necessary for our clients or not. Additionally, we can continue the conversation on Discord of Qdrant if you prefer. I will be available, so please feel free to reach out to me anytime.
In case of future updates and features from Qdrant, we should increase the adaptability of our library. With this proposed change, as soon as Qdrant introduces new features, users of this library can instantly integrate and utilize them without having to wait for explicit support in this package.
I'm suggesting two potential paths:
executeRaw
function to the main Qdrant client class. Here's a draft of that function:However, this approach does introduce some code redundancy.
AbstractEndpoint
: Instead of direct implementation, we can modify thecreateRequest
method inAbstractEndpoint
to be public and static. This way, we centralize the request creation process.Given this modification, the
executeRaw
function within the main client becomes:@hkulekci, which approach aligns more with our vision for the library? Once we decide, I'll be happy to draft a PR for review.
The text was updated successfully, but these errors were encountered: