Issue 4446: Make sure that the new Neo4j Vector Type is supported in APOC extended #4456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4446
[WIP]
Note:
To use vector at the moment we have to test it with an enterprise and this config:
I tried testing using
DbmsRule
but they were not working (in general, with community editions)They gave error "storing properties of type vector is not supported in aligned store format"
Also on apoc core they were done the same way but probably they were done with a different version from 2025.07 released publicly.
Waiting for docker 2025.07-enterprise
WAITING FOR DRIVERS VERSION FULLY SUPPORTING VECTOR TYPES
Currently the driver support writing node with vector types, even with the latest one (neo4j-java-driver/6.0.0-beta01) but it seems that the reading is not fully supported, so that is difficult to test that the vector will be correctly exported/imported
Maybe we had to wait for the vector not to be
internal.
?