_id
, _key
and _rev
of the document which was written.created
, updated
or deleted
._id
of the document whose change it records. Every event is associated with a corresponding command that records the changes caused by that event.{}
) to the document's JSON representation.{}
)._id
matches a specified glob pattern (barring documents within RecallGraph's own service collections). The pattern is passed as a query parameter._id
matches a specified brace pattern (barring documents within RecallGraph's own service collections). The pattern is passed as a query parameter./
- The root path. This tells the log builder to basically pick everything - the entire database for logging - every user-defined collection and every document (vertex/edge) (existing and deleted) therein. This is essentially the Database Scope./g/<glob pattern>
- Named Graph. A path that starts with /g/
followed by a valid glob pattern. This is essentially the Graph Scope./c/<glob pattern>
- Collection. A path that starts with /c/
followed by a valid glob pattern. This is essentially the Collection Scope./ng/<glob pattern>
- Node Glob. A path that starts with /ng/
followed by a valid glob pattern. This is essentially the Node-Glob Scope./n/<brace pattern>
- Node Brace. A path that starts with /n/
followed by a valid brace pattern. This is essentially the Node-Brace Scope. This is much faster than a node-glob scan, and should be the preferred document selection pattern wherever possible.