Ah OK, I will try to see the documentation for installing from source.
Thanks!
since it contains untested code. so you might find a few features lacking
i will update the page
fixed
I downloaded the latest release, RecallGraph and CivicGraph: CivicGraph installs fine, RecallGraph has the same error: "Services: 3103. failed to invoke module Reason: ArangoError 3100: cannot locate module File: jsep File: /var/folders/lz/c36rl6hx3glb32zyz502js200000gn/T/arangod_DaPjx4/services-tmp-593-37130413/lib/operations/filter/helpers.js". I will work with CivicGraph.
CivicGraph is well tested. However, you will find some features missing that you would have seen in the demo
Just popping up to say that this project is exactly what I was looking for. I can't wait for more robust documentation. One question... Is there a way to purge history? For example, our regression tests delete the objects from a previous test to start from a clean slate. I'd like to request something like "purge all history before <time>".
The purge option has been on my mind, but with a slightly different use case (delete event records for an entity/s to comply with privacy and/or security requirements, eg. GDPR). However, purging by timestamp, although possible, is something I would be reluctant to implement as it is susceptible to potential misuse/abuse. In general, if a user wishes to purge an event trail for some entities, they should be forced to explicitly specify those entity ids, to make sure they know what they are deleting.
@adityamukho Thanks. Performance is always a hot-spot in my work. As long as you keep it backwards compatible, I'm thrilled. For our regression testing, I can truncate your tables at the start of each test so I'm not too concerned. I'm concerned about resources in an active database that runs for years so we may want to have a way to (at least) archive ancient data. I'm not concerned about someone trashing the tables since users have to go through another application layer to get to the database so we can lock down this feature absolutely necessary.
is arangodb and RecallGraph Foxx app Api is different?
Foxx apps provide a micro-service that extends the ArangoDB API. RecallGraph provides an http listener to provide additional features. In this case, you can consider RecallGraph to be a proxy between your requests and the database. For instance, instead of calling the ArangoDB interface to insert an object, you would use the RecallGraph interface.
In my case, historical information is needed so the customer can compare an old version to a new version. We have a logger that will let us know who made each modification so the customer will know who to talk to if things aren't right.
oh i need same type of logic
do you also save customer name who changed document with document?
Our documents are virtual entities used to design Integrated Circuits. As such the keys are relatively fixed in semantics and structure. The key is the circuit template object which is a graph of interconnected templates that ultimately resolve to the components used in the design. These templates change over time by the developers. We want to answer two questions. 1) What changed between two versions of the template graph that caused the change in the components? 2) What specific change caused this difference and who do we talk to to find out why? I'm hoping that RecallGraph will allow me answer these questions. I was originally going just to track the template objects, but a general solution would make it more flexible for the future.
can i write RecallGraph like queries myself , so i can make AQL queries work?
in my own server, without using foxx service?