-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The Pinecone APOC implementation is misleading #4242
Labels
Comments
vga91
added a commit
that referenced
this issue
Nov 26, 2024
vga91
added a commit
that referenced
this issue
Nov 29, 2024
RobertoSannino
pushed a commit
that referenced
this issue
Dec 2, 2024
vga91
added a commit
that referenced
this issue
Dec 5, 2024
vga91
added a commit
that referenced
this issue
Dec 10, 2024
vga91
added a commit
that referenced
this issue
Dec 16, 2024
vga91
added a commit
that referenced
this issue
Dec 19, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
In Pinecone, a collection is a backup of a (hardware) based index, and the index is what "we" consider to be a collection
but the existing implementation queries for info /collections, which is wrong, it uses apoc extended uses
pinecone/collections/<name>
, but it should bepinecone/indexes/<name>.
..What Pinecone calls collections are backups of pod based indexes.
What apoc / we call "collection" are simply indexes in pinecone.
How to change
Change everything to
index
but keep the procedure names as-is, to be consistent with the other onesThe text was updated successfully, but these errors were encountered: