-
Notifications
You must be signed in to change notification settings - Fork 495
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
Better error messaging with vectordb query/get procedures #4121
Labels
Comments
vga91
changed the title
Better error messaging with apoc.vectordb.weaviate.createCollection procedure
Better error messaging with apoc.vectordb.weaviate.query procedure
Jul 1, 2024
vga91
changed the title
Better error messaging with apoc.vectordb.weaviate.query procedure
Better error messaging with vectordb query/get procedures
Jul 2, 2024
vga91
added a commit
that referenced
this issue
Jul 2, 2024
vga91
added a commit
that referenced
this issue
Jul 3, 2024
RobertoSannino
pushed a commit
that referenced
this issue
Jul 3, 2024
github-project-automation
bot
moved this from Review
to Done (to cherry-pick)
in APOC Extended Larus
Jul 4, 2024
vga91
added a commit
to vga91/neo4j-apoc-procedures
that referenced
this issue
Jul 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following procedure should return the root cause (i.e. embedding size different from the other ones in the collection):
Edit:
Unlike the other vector procedures that return an HTTP error (see here),
this procedure returns 200 OK but with an "errors" key in the JSON response
The text was updated successfully, but these errors were encountered: