AWS neptune documentation change
Summary
Fixed typo in 'quad statement indexes' from 'statment' to 'statement'
Security assessment
The change is a simple typo correction with no security implications.
Diff
diff --git a/neptune/latest/userguide/feature-overview-storage-indexing.md b/neptune/latest/userguide/feature-overview-storage-indexing.md index 1124b134a..5e456cc32 100644 --- a//neptune/latest/userguide/feature-overview-storage-indexing.md +++ b//neptune/latest/userguide/feature-overview-storage-indexing.md @@ -11 +11 @@ When you query a graph of quads, for each quad position, you can either specify -Neptune uses indexes to resolve graph queries patterns. These indexes are over the four primary components of a graph edge: Subject (source vertex in LPG); Predicate (RDF), or Property or Edge Label (LPG); Object (target vertex or property value in LPG); and Graph (RDF) or Edge Identifier (LPG). There are 16 (2^4) possible access patterns for these four quad component positions. You can query all 16 patterns efficiently without having to scan and filter by using six indexes. Each quad statement index uses a key that is composed of the four position values concatenated in a different order. One possible combination of quad statment indexes that would cover all 16 access paths is: +Neptune uses indexes to resolve graph queries patterns. These indexes are over the four primary components of a graph edge: Subject (source vertex in LPG); Predicate (RDF), or Property or Edge Label (LPG); Object (target vertex or property value in LPG); and Graph (RDF) or Edge Identifier (LPG). There are 16 (2^4) possible access patterns for these four quad component positions. You can query all 16 patterns efficiently without having to scan and filter by using six indexes. Each quad statement index uses a key that is composed of the four position values concatenated in a different order. One possible combination of quad statement indexes that would cover all 16 access paths is: