Document VECTOR type and new vector functions
#1299
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gem-neo4j
reviewed
Jun 9, 2025
modules/ROOT/pages/expressions/predicates/type-predicate-expressions.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Show resolved
Hide resolved
gem-neo4j
reviewed
Jun 10, 2025
| @@ -26,7 +27,7 @@ In this example `VECTOR` type value, `[1.05, 0.123, 5]` is the coordinates of th | |||
| [NOTE] | |||
| The dimensions and the formatting of a `VECTOR` is similar to a xref:values-and-types/lists.adoc[`LIST`] value. | |||
| However, unlike `LIST` values which contain elements that can be accessed individually with xref:expressions/list-expressions.adoc[list expressions], all operations on a `VECTOR` must operate on the entire `VECTOR`; it is not possible to access or slice individual dimensions of a `VECTOR` value. | |||
| Additionally, a `LIST` cannot contain `VECTOR` values. | |||
| Additionally, a `LIST` cannot store `VECTOR` values. | |||
There was a problem hiding this comment.
Neo4j cannot store Lists containing vector values, slight difference
gem-neo4j
reviewed
Jun 10, 2025
|
|
||
| | If a `STRING` is used in `vectorValue`, it must start and end with square brackets (`[]`). | ||
| The values inside the brackets must be a number represented in either decimal or scientific notation and must be comma separated. | ||
| | `null`, `NaN`, and `Infinity` values are not allowed as elements in the `LIST` used as `vectorValue`. |
There was a problem hiding this comment.
Maybe:
Suggested change
| | `null`, `NaN`, and `Infinity` values are not allowed as elements in the `LIST` used as `vectorValue`. | |
| | `null`, `NaN`, and `Infinity` values are not allowed as coordinate values. |
gem-neo4j
reviewed
Jun 25, 2025
|
This PR includes documentation updates New pages: Updated pages: |
Hunterness
reviewed
Jul 2, 2025
| @@ -13,21 +12,22 @@ This section will first provide a brief overview of each type, and then go into | |||
|
|
|||
| A property type value is one that can be stored as a node or relationship property. | |||
|
|
|||
| Property types are the most primitive types in Cypher and include the following: `BOOLEAN`, `DATE`, `DURATION`, `FLOAT`, `INTEGER`, `LIST`, `LOCAL DATETIME`, `LOCAL TIME`, `POINT`, `STRING`, `ZONED DATETIME`, and `ZONED TIME`. | |||
| Property types are the most primitive types in Cypher and include the following: `BOOLEAN`, `DATE`, `DURATION`, `FLOAT`, `INTEGER`, `LIST`, `LOCAL DATETIME`, `LOCAL TIME`, `POINT`, `STRING`, `VECTOR` (introduced in Neo4j 2025.xx) `ZONED DATETIME`, and `ZONED TIME`. | |||
There was a problem hiding this comment.
Suggested change
| Property types are the most primitive types in Cypher and include the following: `BOOLEAN`, `DATE`, `DURATION`, `FLOAT`, `INTEGER`, `LIST`, `LOCAL DATETIME`, `LOCAL TIME`, `POINT`, `STRING`, `VECTOR` (introduced in Neo4j 2025.xx) `ZONED DATETIME`, and `ZONED TIME`. | |
| Property types are the most primitive types in Cypher and include the following: `BOOLEAN`, `DATE`, `DURATION`, `FLOAT`, `INTEGER`, `LIST`, `LOCAL DATETIME`, `LOCAL TIME`, `POINT`, `STRING`, `VECTOR` (introduced in Neo4j 2025.xx), `ZONED DATETIME`, and `ZONED TIME`. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
TO-DO:
NOT in this PR:
See also: #1325