Skip to content

Conversation

vga91
Copy link
Collaborator

@vga91 vga91 commented Aug 4, 2025

Fixes #4446

  • cherry-pick in dev

[WIP]
Note:
To use vector at the moment we have to test it with an enterprise and this config:

internal.cypher.enable_vector_type=true

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

        // --- session.run("MATCH (n) RETURN n").list() ---
        /* throws error:

            org.neo4j.driver.internal.util.ErrorUtil$InternalExceptionCause
            detailMessage = "Struct tag: 0x56 representing type VECTOR is not supported for this protocol version"
            cause = {Neo4jException@7483} "org.neo4j.driver.exceptions.Neo4jException: 22NBD: Unsupported struct tag: 0x56."
         */

Maybe we had to wait for the vector not to be internal.?

@vga91 vga91 marked this pull request as draft August 4, 2025 10:25
@vga91 vga91 changed the title Issue 4446 Issue 4446: Make sure that the new Neo4j Vector Type is supported in APOC extended Aug 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant