AWS neptune documentation change
Summary
Updated documentation for the 'updateSingleCardinalityProperties' parameter to indicate it is now supported for openCypher loads and clarified how it controls property updates.
Security assessment
The changes clarify functionality of a data loading parameter but contain no evidence of addressing vulnerabilities. The update enables property value updates during loading which could impact data integrity if misused, but doesn't reference security fixes or vulnerabilities.
Diff
diff --git a/neptune/latest/userguide/load-api-reference-load.md b/neptune/latest/userguide/load-api-reference-load.md index 5ce38cad3..ae8c75d06 100644 --- a//neptune/latest/userguide/load-api-reference-load.md +++ b//neptune/latest/userguide/load-api-reference-load.md @@ -323 +323 @@ For more information, see [SPARQL Default Graph and Named Graphs](./feature-spar - * **`updateSingleCardinalityProperties`** – This is an optional parameter that controls how the bulk loader treats a new value for single-cardinality vertex or edge properties. This is not supported for loading openCypher data (see Loading openCypher data). + * **`updateSingleCardinalityProperties`** – This is an optional parameter that controls how the bulk loader treats a new value for single-cardinality vertex or edge properties. @@ -384 +384 @@ For more information, see [Access keys (access key ID and secret access key)](ht - * The `updateSingleCardinalityProperties` parameter is not supported for openCypher loads because all openCypher properties have single cardinality. The openCypher load format does not support arrays, and if an ID value appears more than once, it is treated as a duplicate or an insertion error (see below). + * The `updateSingleCardinalityProperties` parameter is supported for openCypher loads. All openCypher properties have single cardinality, and if an ID value appears more than once, it is treated as a duplicate or an insertion error (see below). @@ -396 +396 @@ For more information, see [Access keys (access key ID and secret access key)](ht - * The loader never updates property values of an existing node or relationship in the database if it encounters load data having the ID of the existing node or relationship. However, it does load node labels and properties that are not present in the existing node or relationship. + * By default, the loader does not update property values of an existing node or relationship in the database if it encounters load data having the ID of the existing node or relationship. However, it does load node labels and properties that are not present in the existing node or relationship. To update existing property values, set `updateSingleCardinalityProperties` to `"TRUE"`.