forked from arangodb/arangodb
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[GORDO-1571] historic pregel access (arangodb#18366)
* started work on extending api command_pregel. Right now reading a single pid tested by collection and api. * do NOT forward history requests, jslint * added pregel read history (optional: pid) javascript modules (shell client(js) and shell sherver(v8)) * add getHistory method and deleteHistoyr method to the JS modules (client http and server v8). handled strange internal api error case * jslint * ..... js & v8 hate * ..... jslint * special handling also in v8 - gut. added placeholder for further tests. * implemented addition get all history tests * truncate handling was incorrect. fixed this. some hopefully last adjustments. tests finalized. * <WIP> trx.all cannot be used like that <WIP> * for reads, now uses query instead of a transaction as the solution before is not working in a clustered environment. * handle returned Slices (inside OperationResult) in case they are none). Will return a TrueSlice in that specific case now. Also adjusted js tests. * some rework on what we actually write. This is still a partial TODO as the solution does not look like how I thought it would be! * remove not used builder * proper error message in v8 removeHistory * remove not needed builder * added changelog * build error fix * Finished sentence. --------- Co-authored-by: Aditya Mukhopadhyay <aditya@arangodb.com>
- Loading branch information
Showing
13 changed files
with
874 additions
and
191 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.