Introduce application/vnd.neo4j.query.v1.1 #9
Conversation
This version introduces VECTOR and UNSUPPORTED types.
| The dimension of the `VECTOR` is implicitly defined by the length of the `coordinates` array. | ||
|
|
||
| | UNSUPPORTED | ||
| | Unsupported |
There was a problem hiding this comment.
All drivers called this UnknownType. Are we sure we don't want to do the same in this API?
There was a problem hiding this comment.
The java driver expose in the type system as UNSUPPORTED, so we changed to match them. See, https://github.com/neo4j/neo4j-java-driver/blob/6.x/driver/src/main/java/org/neo4j/driver/types/UnsupportedType.java.
There was a problem hiding this comment.
As I understand it the class type users get exposed to is https://neo4j.com/docs/api/java-driver/current/org.neo4j.driver/org/neo4j/driver/internal/value/UnsupportedTypeValue.html , which implements https://neo4j.com/docs/api/java-driver/current/org.neo4j.driver/org/neo4j/driver/types/UnsupportedType.html. UNSUPPORTED is the Bolt name, or?
There was a problem hiding this comment.
This value goes into a field called $type, so call it UNSUPPORTED instead of UNSUPPORTED TYPE removes the redundancy.
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
3 participants
This version introduces VECTOR and UNSUPPORTED types.