-
Notifications
You must be signed in to change notification settings - Fork 494
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
The apoc.vectordb.milvus.query*
and apoc.vectordb.weaviate.query*
procedures should get the fields config from metadataKey if present.
#4231
Labels
Comments
vga91
pushed a commit
that referenced
this issue
Nov 20, 2024
…te.query* procedures should get the fields config from metadataKey if present
vga91
added a commit
that referenced
this issue
Nov 20, 2024
…te.query* procedures should get the fields config from metadataKey if present
vga91
added a commit
that referenced
this issue
Nov 29, 2024
…te.query* procedures should get the fields config from metadataKey if present
vga91
added a commit
that referenced
this issue
Dec 3, 2024
…te.query* procedures should get the fields config from metadataKey if present
vga91
added a commit
that referenced
this issue
Dec 4, 2024
…te.query* procedures should get the fields config from metadataKey if present
github-project-automation
bot
moved this from Review
to Done (check if cherry-pick)
in APOC Extended Larus
Dec 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
apoc.vectordb.milvus.query*
andapoc.vectordb.weaviate.query*
procedures should get the fields config from metadataKey if present.Expected Behavior (Mandatory)
It should get the
fields
config frommapping.mappingKey
configActual Behavior (Mandatory)
It fails with error:
How to Reproduce the Problem
Execute:
The text was updated successfully, but these errors were encountered: