1
0
Fork 0
Commit Graph

273 Commits

Author SHA1 Message Date
jsteemann 7fb536387d move replication-dump into engine 2017-03-21 13:55:57 +01:00
Michael Hackstein 5eecac958f Removed accidently commited log output 2017-03-14 09:13:45 +01:00
Michael Hackstein 83663c47b2 Deleted CollectionResult. It is identical to arangodb::Result introduced later. 2017-03-10 17:18:12 +02:00
jsteemann aa8160fc3d try to fix non-enterprise compile error 2017-03-06 18:09:43 +01:00
jsteemann cf5d20ddee Merge branch 'devel' of https://github.com/arangodb/arangodb into devel 2017-02-28 17:02:42 +01:00
jsteemann b6a265068a fix velocypack-over-HTTP responses 2017-02-28 17:01:59 +01:00
Michael Hackstein a884ee2bfb Intermediate commit. Moved many toVPack functions of LogicalCollection to a unified vpack + ignore-keys alternative. This commit is used to run all tests everywhere. May be red 2017-02-27 13:01:07 +01:00
jsteemann 0909ffe69b moved helper functions into their own file 2017-02-14 13:44:54 +01:00
jsteemann 5ebeb5f144 Merge branch 'devel' of https://github.com/arangodb/arangodb into engine-api 2017-02-13 16:29:40 +01:00
Kaveh Vahedipour 6a5d61c2f1 avoidServers correctly in again 2017-02-13 16:00:30 +01:00
jsteemann 7e690a0c61 renaming 2017-02-13 15:18:40 +01:00
jsteemann eb73dbf960 renaming 2017-02-13 13:30:57 +01:00
jsteemann d024a6d00a remove logging for non-topics 2017-02-10 09:32:50 +01:00
Max Neunhoeffer bde48d524d Change undocumented behaviour in case of invalid rev in JS document ops.
An invalid rev should lead to a 1200 ("conflict") error rather than a
1239 ("illegal document revision") error. This is more intuitive and
in line with the corresponding change in the HTTP API. No tests needed
adjustment.
2017-02-08 10:59:04 +01:00
Max Neunhoeffer 883c11ea45 Handle the case that ClusterComm is already shut down gracefully.
This touches every single place where ClusterComm is being used.
2017-02-07 15:31:40 +01:00
Max Neunhoeffer 71dae630c3 Store ClusterComm singleton in shared_ptr. 2017-02-06 15:25:18 +01:00
jsteemann 3c5edeb9b2 fix cluster AQL statistics 2017-02-03 11:47:36 +01:00
jsteemann d96ce9af37 Merge branch 'devel' of https://github.com/arangodb/arangodb into engine-api 2017-01-30 12:53:10 +01:00
jsteemann 0cb7d416d0 moved transaction collections into their own files 2017-01-26 16:51:57 +01:00
Michael Hackstein 41f0ac974b Moved creation of Cluster collection from V8Server to ClusterMethods. Also introduced a static class wrapper for Methods. 2017-01-16 12:40:05 +01:00
Andreas Streichardt 15fab0b7ce Do not initialize clustercomm twice in debug mode 2017-01-06 11:58:26 +01:00
Andreas Streichardt 06a0fc11cd Add Sync Replication debug code 2017-01-04 15:51:47 +01:00
jsteemann 4d76ef962b added count(details = true) for sharded collections 2016-12-13 16:03:49 +01:00
jsteemann b96897e296 fixed some issues detected by coverity build tool 2016-12-12 15:41:54 +01:00
Andreas Streichardt 10f7d75651 Fix uniform shard distribution when creating collections 2016-12-07 18:38:15 +01:00
Andreas Streichardt 11bd9381d5 Add satellite collections 2016-12-06 16:40:50 +01:00
Kaveh Vahedipour ffe7f9f3ad merged in devel 2016-11-16 14:59:53 +01:00
jsteemann 77e2cf5a65
fix passing of special chars in URLs in cluster
- this sets option CURLOPT_PATH_AS_IS to keep ".." and other special components in paths
- this also changes the behavior of StringUtils::urlEncode() to always encode the "."
  character to "%2e"
2016-11-15 15:46:22 +01:00
jsteemann 5f65a9ed4f allow more control over handling of pre-3.1 _rev values
this changes the server startup option `--database.check-30-revisions` from a boolean (true/false)
parameter to a string parameter with the following possible values:

- "fail":
  will validate _rev values of 3.0 collections on collection loading and throw an exception when invalid _rev values are found.
  in this case collections with invalid _rev values are marked as corrupted and cannot be used in the ArangoDB 3.1 instance.
  the fix procedure for such collections is to export the collections from 3.0 database with arangodump and restore them in 3.1 with arangorestore.
  collections that do not contain invalid _rev values are marked as ok and will not be re-checked on following loads.
  collections that contain invalid _rev values will be re-checked on following loads.

- "true":
  will validate _rev values of 3.0 collections on collection loading and print a warning when invalid _rev values are found.
  in this case collections with invalid _rev values can be used in the ArangoDB 3.1 instance.
  however, subsequent operations on documents with invalid _rev values may silently fail or fail with explicit errors.
  the fix procedure for such collections is to export the collections from 3.0 database with arangodump and restore them in 3.1 with arangorestore.
  collections that do not contain invalid _rev values are marked as ok and will not be re-checked on following loads.
  collections that contain invalid _rev values will be re-checked on following loads.

- "false":
  will not validate _rev values on collection loading and not print warnings.
  no hint is given when invalid _rev values are found.
  subsequent operations on documents with invalid _rev values may silently fail or fail with explicit errors.
  this setting does not affect whether collections are re-checked later.
  collections will be re-checked on following loads if `--database.check-30-revisions` is later set to either `true` or `fail`.

The change also suppresses warnings that were printed when collections were restored using arangorestore, and the restore
data contained invalid _rev values. Now these warnings are suppressed, and new HLC _rev values are generated for these documents
as before.
2016-11-04 23:17:01 +01:00
Michael Hackstein a7f63b3a53 Removed dead code of TraverserExpressions. They have been replaced by native AQL expressions everywhere. 2016-11-04 18:15:04 +01:00
jsteemann 7efabd3706 fix revision id handling 2016-10-28 13:44:55 +02:00
Frank Celler e4ba82e8e9 rewrite of AgencyComm 2016-10-23 00:46:30 +02:00
Max Neunhoeffer 039ca9aceb Increase some timeouts from 60 to 90s to be more load tolerant. 2016-10-13 12:52:59 +02:00
Max Neunhoeffer 82e548ff8b Change setup of getResponsibleShard w.r.t. collection. 2016-10-07 21:05:18 +02:00
Max Neunhoeffer 58f892fd92 Fix /_api/edges and thus some enterprise tests. 2016-10-05 14:01:46 +02:00
Max Neunhoeffer 15cbd0adab Fix a typo. 2016-10-05 13:44:23 +02:00
Max Neunhoeffer a023c609d0 Fix a typo. 2016-09-30 16:40:53 +02:00
Max Neunhoeffer 5cd913e003 Fix error handling for ClusterInfo::getCollection. 2016-09-30 14:11:46 +02:00
Michael Hackstein acdcb3b76a Modified collection creation in cluster. It now does not require access to V8 objects any more. 2016-09-26 10:45:28 +02:00
jsteemann 9611f30796 Merge branch 'devel' of https://github.com/arangodb/arangodb into generic-col-types 2016-09-07 11:44:49 +02:00
Kaveh Vahedipour a37d073813 a candidate of a leader could ask a strarting up agent for a vote before it having a vocbase. 2016-09-07 11:02:15 +02:00
Michael Hackstein e22014a272 Merge branch 'MIT' of github.com:arangodb/arangodb into generic-col-types 2016-09-06 09:33:23 +02:00
jsteemann 4492409d5f Merge branch 'devel' of https://github.com/arangodb/arangodb into generic-col-types 2016-09-02 15:23:15 +02:00
Kaveh Vahedipour b3b7d7c907 failed servers are excluded from new shard creation 2016-09-02 12:37:53 +02:00
Michael Hackstein 3c851f8687 Added proper error handling for collection not found in V8 2016-09-01 17:42:27 +02:00
Michael Hackstein 81bc1c67e7 Fixed filtered edges for an empty list of expressions. 2016-09-01 11:40:48 +02:00
jsteemann baad30fdb7 Merge branch 'devel' of https://github.com/arangodb/arangodb into generic-col-types 2016-08-30 16:47:35 +02:00
Jan Steemann 226ed6d17a slighty improved error handling in import API 2016-08-30 16:33:44 +02:00
jsteemann c5f847a912 fix figures and volatile collection counts 2016-08-24 14:35:55 +02:00
Jan Christoph Uhde 1febeadfd7 finish ResponseCode enum 2016-08-23 15:46:42 +02:00