-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
Add option to use _additional fields while executing a Weaviate query #5072
Comments
jettro
added a commit
to jettro/langchain-weaviate-additional
that referenced
this issue
May 22, 2023
Implementation is similar to search_distance and where_filter
jettro
added a commit
to jettro/langchain-weaviate-additional
that referenced
this issue
May 22, 2023
Add the additional part also to the vector based query
jettro
added a commit
to jettro/langchain-weaviate-additional
that referenced
this issue
May 22, 2023
dev2049
added a commit
that referenced
this issue
May 23, 2023
Implementation is similar to search_distance and where_filter # adds 'additional' support to Weaviate queries Co-authored-by: Dev 2049 <[email protected]>
vowelparrot
pushed a commit
that referenced
this issue
May 24, 2023
Implementation is similar to search_distance and where_filter # adds 'additional' support to Weaviate queries Co-authored-by: Dev 2049 <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
Weaviate has the option to pass _additional field while executing a query
https://weaviate.io/developers/weaviate/api/graphql/additional-properties
It would be good to be able to use this feature and add the response to the results. It is a small change, without breaking the API. We can use the kwargs argument, similar to where_filter in the python class weaviate.py.
Motivation
When comparing and understanding query results, using certainty is a good way.
Your contribution
I like to contribute to the PR. As it would be my first contribution, I need to understand the integration tests and build the project, and I already tested the change in my local code sample.
The text was updated successfully, but these errors were encountered: