description |
---|
A record of what changed between successive versions |
- Post-filter in read endpoints -
log
,diff
,show
. - k Shortest Paths - Custom-weighted, point-in-time, shortest paths between endpoints.
- Synchronous skeleton graph updates within commit transactions.
- OpenTracing instrumentation, using ancillary collector foxx service. Non-intrusive and strictly optional.
- Logs can be grouped by type (vertex/edge).
- Explicit Commits to sync event log with writes that occurred outside of RecallGraph's API methods.
- Providers for all API endpoints to let other dependent Foxx services invoke RecallGraph's service methods directly, using ArangoDB's service linking mechanism.
- Purge endpoint to remove all history for nodes at a specified path.
- Restore endpoint to undelete nodes that were deleted through RecallGraph's API.
- Paths are returned in traverse calls, with support for path filters.
- Support for slicing in show endpoint when aggregation is enabled.
- Data:
- Event objects have a
collection
field to identify the collection to which their corresponding document belongs. - Skeleton graph objects have a
collection
field to identify the collection to which their corresponding document belongs. - Origin events have
meta.id
,hops-from-origin
,collection
,ctime
andevent
fields to allow building dense indexes on them. - Migration script to automatically upgrade event and skeleton trees created using older versions.
- Migration script to remove stale indices.
- Event objects have a
- Precision limiters for timestamp parameters.
- Dedicated
filter
endpoint. All read endpoints now have their own filtering capability. - Asynchronous skeleton graph updates in cron jobs.
- Breaking:
returnCommands
parameter removed fromlog
. Anything that depended on this should now use the enhanceddiff
endpoint instead.groupSkip
andgroupLimit
removed fromdiff
endpoint, as they were deemed not useful. The newly available post-filter param can indirectly help make up for the deficit in most cases.- Service collection suffixes are no longer configurable (extraneous config).
- Bug:
- Sort direction was not being honored in
log
whengroupBy
was specified. This has been fixed. - Hard-coded service collection name in a query for
show
was removed. traverse
no longer breaks if starting vertex is not found.- Fixed operation id for the
UPDATE
route, which was incorrectly marked asreplace
.
- Sort direction was not being honored in
- Document operations are checked first for compatible last events before executing.
- Data:
- Collection origin events have their
origin-for
field renamed tocollection
to remain consistent with field naming convention followed for regular events. - Certain indices have changed - primarily, sparse indexes have been replaced by their dense counterparts.
- When replacing/updating an existing document with no event log record, a
created
event is recorded instead of anupdated
event.
- Collection origin events have their
- Breaking:
- Diffs are enhanced to return some event metadata along with command lists. This is to reduce overloading the
log
function with event+command-related queries. - The
countsOnly
parameter now has an effect even whengroupBy
isnull
forlog
endpoints. It returns the overall total number of events based on the filters provided. show
returns an array with total count whengroupBy
isnull
, instead of a bare object. This is for consistent post-filter application semantics.traverse
minDepth
has been changed from0
to1
.
- Diffs are enhanced to return some event metadata along with command lists. This is to reduce overloading the