arangodb (2.3.5-1.1) stable; urgency=low * Changed to Version 2.3.5 * fixed intermittent 404 errors in Foxx apps after mounting or unmounting apps * fixed issue #1200: Expansion operator results in "Cannot call method 'forEach' of null" * fixed issue #1199: Cannot unlink root node of plan -- ArangoDB Maintainer Fri, 16 Jan 2015 16:53:20 +0100 arangodb (2.3.4-1.1) stable; urgency=low * Changed to Version 2.3.4 * fixed cerberus path for MyArangoDB -- ArangoDB Maintainer Tue, 23 Dec 2014 12:33:06 +0100 arangodb (2.3.3-1.1) stable; urgency=low * Changed to Version 2.3.3 * fixed error handling in instanciation of distributed AQL queries, this also fixes a bug in cluster startup with many servers * issue #1185: parse non-fractional JSON numbers with exponent (e.g. `4e-261`) * issue #1159: allow --server.request-timeout and --server.connect-timeout of 0 -- ArangoDB Maintainer Wed, 17 Dec 2014 15:48:20 +0100 arangodb (2.3.2-1.1) stable; urgency=low * Changed to Version 2.3.2 * fixed issue #1173: AQL Editor "Save current query" resets user password * fixed missing makeDirectory when fetching a Foxx application from a zip file * put in warning about default changed: fixed issue #1134: Change the default endpoint to localhost * fixed issue #1163: invalid fullCount value returned from AQL * fixed range operator precedence * limit default maximum number of plans created by AQL optimizer to 256 (from 1024) * make AQL optimizer not generate an extra plan if an index can be used, but modify existing plans in place * fixed AQL cursor ttl (time-to-live) issue Any user-specified cursor ttl value was not honored since 2.3.0. * fixed segfault in AQL query hash index setup with unknown shapes * fixed memleaks * added AQL optimizer rule for removing `INTO` from a `COLLECT` statement if not needed * fixed issue #1131 This change provides the `KEEP` clause for `COLLECT ... INTO`. The `KEEP` clause allows controlling which variables will be kept in the variable created by `INTO`. * fixed issue #1147, must protect dispatcher ID for etcd -- ArangoDB Maintainer Wed, 10 Dec 2014 00:28:41 +0100 arangodb (2.3.1-1.1) stable; urgency=low * Changed to Version 2.3.1 * recreate password if missing during upgrade * fixed issue #1126 * fixed non-working subquery index optimizations * do not restrict summary of Foxx applications to 60 characters * fixed display of "required" path parameters in Foxx application documentation * added more optimizations of constants values in AQL FILTER conditions * fixed invalid or-to-in optimization for FILTERs containing comparisons with boolean values * fixed replication of `_graphs` collection * added AQL list functions `PUSH`, `POP`, `UNSHIFT`, `SHIFT`, `REMOVE_VALUES`, `REMOVE_VALUE`, `REMOVE_NTH` and `APPEND` * added AQL functions `CALL` and `APPLY` to dynamically call other functions * fixed AQL optimizer cost estimation for LIMIT node * prevent Foxx queues from permanently writing to the journal even when server is idle * fixed AQL COLLECT statement with INTO clause, which copied more variables than v2.2 and thus lead to too much memory consumption. This deals with #1107. * fixed AQL COLLECT statement, this concerned every COLLECT statement, only the first group had access to the values of the variables before the COLLECT statement. This deals with #1127. * fixed some AQL internals, where sometimes too many items were fetched from upstream in the presence of a LIMIT clause. This should generally improve performance. -- ArangoDB Maintainer Sat, 29 Nov 2014 15:47:05 +0100 arangodb (2.3.0-1.1) stable; urgency=low * Changed to Version 2.3.0 * fixed syslog flags. `--log.syslog` is deprecated and setting it has no effect, `--log.facility` now works as described. Application name has been changed from `triagens` to `arangod`. It can be changed using `--log.application`. The syslog will only contain the actual log message. The datetime prefix is omiited. * fixed deflate in SimpleHttpClient * hide system applications in **Applications** tab by default Display of system applications can be toggled by using the *system applications* toggle in the UI. * added HTTP REST API for managing tasks (`/_api/tasks`) * allow passing character lists as optional parameter to AQL functions `TRIM`, `LTRIM` and `RTRIM` These functions now support trimming using custom character lists. If no character lists are specified, all whitespace characters will be removed as previously: TRIM(" foobar\t \r\n ") // "foobar" TRIM(";foo;bar;baz, ", "; ") // "foo;bar;baz" * added AQL string functions `LTRIM`, `RTRIM`, `FIND_FIRST`, `FIND_LAST`, `SPLIT`, `SUBSTITUTE` * added AQL functions `ZIP`, `VALUES` and `PERCENTILE` * made AQL functions `CONCAT` and `CONCAT_SEPARATOR` work with list arguments * dynamically create extra dispatcher threads if required * fixed issue #1097: schemas in the API docs no longer show required properties as optional -- ArangoDB Maintainer Tue, 18 Nov 2014 19:02:18 +0100 arangodb (2.3.0b2-1.1) stable; urgency=low * Changed to Version 2.3.0-beta2 * front-end: new icons for uploading and downloading JSON documents into a collection * front-end: fixed documents pagination css display error * front-end: fixed flickering of the progress view * front-end: fixed missing event for documents filter function * front-end: jsoneditor: added CMD+Return (Mac) CTRL+Return (Linux/Win) shortkey for saving a document * front-end: added information tooltip for uploading json documents. * front-end: added database management view to the collapsed navigation menu * front-end: added collection truncation feature * fixed issue #1086: arangoimp: Odd errors if arguments are not given properly * performance improvements for AQL queries that use JavaScript-based expressions internally * added AQL geo functions `WITHIN_RECTANGLE` and `IS_IN_POLYGON` * fixed non-working query results download in AQL editor of web interface * removed debug print message in AQL editor query export routine * fixed issue #1075: Aardvark: user name required even if auth is off #1075 The fix for this prefills the username input field with the current user's accout name if any and `root` (the default username) otherwise. Additionally, the tooltip text has been slightly adjusted. * fixed issue #1069: Add 'raw' link to swagger ui so that the raw swagger json can easily be retrieved This adds a link to the Swagger API docs to an application's detail view in the **Applications** tab of the web interface. The link produces the Swagger JSON directly. If authentication is turned on, the link requires authentication, too. * documentation updates * added dedicated `NOT IN` operator for AQL Previously, a `NOT IN` was only achievable by writing a negated `IN` condition: FOR i IN ... FILTER ! (i IN [ 23, 42 ]) ... This can now alternatively be expressed more intuitively as follows: FOR i IN ... FILTER i NOT IN [ 23, 42 ] ... * added alternative logical operator syntax for AQL Previously, the logical operators in AQL could only be written as: - `&&`: logical and - `||`: logical or - `!`: negation ArangoDB 2.3 introduces the alternative variants for these operators: - `AND`: logical and - `OR`: logical or - `NOT`: negation The new syntax is just an alternative to the old syntax, allowing easier migration from SQL. The old syntax is still fully supported and will be. * improved output of `ArangoStatement.parse()` and POST `/_api/query` If an AQL query can be parsed without problems, The return value of `ArangoStatement.parse()` now contains an attribute `ast` with the abstract syntax tree of the query (before optimizations). Though this is an internal representation of the query and is subject to change, it can be used to inspect how ArangoDB interprets a given query. * improved `ArangoStatement.explain()` and POST `/_api/explain` The commands for explaining AQL queries have been improved. * added command-line option `--javascript.v8-contexts` to control the number of V8 contexts created in arangod. Previously, the number of V8 contexts was equal to the number of server threads (as specified by option `--server.threads`). However, it may be sensible to create different amounts of threads and V8 contexts. If the option is not specified, the number of V8 contexts created will be equal to the number of server threads. Thus no change in configuration is required to keep the old behavior. However, the default configuration files shipped with ArangoDB have been changed. The number of server threads has been increased in the configuration files, and the number of V8 contexts is now explicitly set in the configuration files (to the same value as the number of server threads was set to in 2.2). If you are using the default config files or merge them with your local config files, please review if the higher default number of server threads is okay in your environment. Additionally you should verify that the number of V8 contexts created (as specified in option `--javascript.v8-contexts`) is okay. * removed index type "bitarray" Bitarray indexes were only half-way documented and integrated in previous versions of ArangoDB so their benefit was limited. The support for bitarray indexes has thus been removed in ArangoDB 2.3. It is not possible to create indexes of type "bitarray" with ArangoDB 2.3. When a collection is openend that contains a bitarray index definition created with a previous version of ArangoDB, ArangoDB will ignore it and log the following warning: index type 'bitarray' is not supported in this version of ArangoDB and is ignored Future versions of ArangoDB may automatically remove such index definitions so the warnings will eventually disappear. * removed internal "_admin/modules/flush" in order to fix requireApp * added basic support for handling binary data in Foxx Requests with binary payload can be processed in Foxx applications by using the new method `res.rawBodyBuffer()`. This will return the unparsed request body as a Buffer object. There is now also the method `req.requestParts()` available in Foxx to retrieve the individual components of a multipart HTTP request. Buffer objects can now be used when setting the response body of any Foxx action. Additionally, `res.send()` has been added as a convenience method for returning strings, JSON objects or buffers from a Foxx action: res.send("

some HTML

"); res.send({ success: true }); res.send(new Buffer("some binary data")); The convenience method `res.sendFile()` can now be used to easily return the contents of a file from a Foxx action: res.sendFile(applicationContext.foxxFilename("image.png")); `fs.write` now accepts not only strings but also Buffer objects as second parameter: fs.write(filename, "some data"); fs.write(filename, new Buffer("some binary data")); `fs.readBuffer` can be used to return the contents of a file in a Buffer object. * improved performance of insertion into non-unique hash indexes significantly in case many duplicate keys are used in the index * issue #1042: set time zone in log output the command-line option `--log.use-local-time` was added to print dates and times in the server-local timezone instead of UTC * command-line options that require a boolean value now validate the -- ArangoDB Maintainer Sat, 08 Nov 2014 00:09:03 +0100 arangodb (2.3.0b1-1.1) stable; urgency=low * Changed to Version 2.3.0-beta1 * added command-line option `--javascript.v8-contexts` to control the number of V8 contexts created in arangod. Previously, the number of V8 contexts was equal to the number of server threads (as specified by option `--server.threads`). However, it may be sensible to create different amounts of threads and V8 contexts. If the option is not specified, the number of V8 contexts created will be equal to the number of server threads. Thus no change in configuration is required to keep the old behavior. * removed bitarray indexes * removed internal "_admin/modules/flush" in order to fix requireApp * added basic support for handling binary data in Foxx Buffer objects can now be used when setting the response body of any Foxx action. Additionally, `res.send()` has been added as a convenience method for returning strings, JSON objects or buffers from a Foxx action: res.send("

some HTML

"); res.send({ success: true }); res.send(new Buffer("some binary data")); The convenience method `res.sendFile()` can now be used to easily return the contents of a file from a Foxx action: res.sendFile(applicationContext.foxxFilename("image.png")); `fs.write` now accepts not only strings but also Buffer objects as second parameter: fs.write(filename, "some data"); fs.write(filename, new Buffer("some binary data")); `fs.readBuffer` can be used to return the contents of a file in a Buffer object. * improved insert performance of non-unique hash index inserts significantly in case many duplicate keys are used in the index * issue #1042: set time zone in log output the command-line option `--log.use-local-time` was added to print dates and times in the server-local timezone instead of UTC * command-line options that require a boolean value now validate the -- ArangoDB Maintainer Sun, 02 Nov 2014 01:08:15 +0100 arangodb (2.3.0a6-1.1) stable; urgency=low * Changed to Version 2.3.0-alpha6 * removed internal "_admin/modules/flush" in order to fix requireApp * added basic support for handling binary data in Foxx Buffer objects can now be used when setting the response body of any Foxx action. Additionally, `res.send()` has been added as a convenience method for returning strings, JSON objects or buffers from a Foxx action: res.send("

some HTML

"); res.send({ success: true }); res.send(new Buffer("some binary data")); The convenience method `res.sendFile()` can now be used to easily return the contents of a file from a Foxx action: res.sendFile(applicationContext.foxxFilename("image.png")); `fs.write` now accepts not only strings but also Buffer objects as second parameter: fs.write(filename, "some data"); fs.write(filename, new Buffer("some binary data")); `fs.readBuffer` can be used to return the contents of a file in a Buffer object. * improved insert performance of non-unique hash index inserts significantly in case many duplicate keys are used in the index * issue #1042: set time zone in log output the command-line option `--log.use-local-time` was added to print dates and times in the server-local timezone instead of UTC * command-line options that require a boolean value now validate the -- ArangoDB Maintainer Wed, 29 Oct 2014 15:30:13 +0100 arangodb (2.3.0a3-1.1) stable; urgency=low * Changed to Version 2.3.0-alpha3 * Added a _relation function in the general-graph module. This deprecated _directedRelation and _undirectedRelation. ArangoDB does not offer any constraints for undirected edges which caused some confusion of users how undirected relations have to be handled. Relation now only supports directed relations and the user can actively simulate undirected relations. * changed return value of Foxx.applicationContext#collectionName: Previously, the function could return invalid collection names because invalid characters were not replaced in the application name prefix, only in the collection name passed. Now, the function replaces invalid characters also in the application name prefix, which might to slightly different results for application names that contained any characters outside the ranges [a-z], [A-Z] and [0-9]. * prevent XSS in AQL editor and logs view * integrated tutorial into ArangoShell and web interface * added option `--backslash-escape` for arangoimp when running CSV file imports * front-end: added download feature for (filtered) documents * front-end: added download feature for the results of a user query * front-end: added function to move documents to another collection * front-end: added sort-by attribute to the documents filter * front-end: added sorting feature to database, graph management and user management view. * issue #989: front-end: Databases view not refreshing after deleting a database * issue #991: front-end: Database search broken * front-end: added infobox which shows more information about a document (_id, _rev, _key) or an edge (_id, _rev, _key, _from, _to). The from and to attributes are clickable and redirect to their document location. * front-end: added edit-mode for deleting multiple documents at the same time. * front-end: added delete button to the detailed document/edge view. * front-end: added visual feedback for saving documents/edges inside the editor (error/success). * front-end: added auto-focusing for the first input field in a modal. * front-end: added validation for user input in a modal. * front-end: user defined queries are now stored inside the database and are bound to the current user, instead of using the local storage functionality of the browsers. The outcome of this is that user defined queries are now independently usable from any device. Also queries can now be edited through the standard document editor of the front-end through the _users collection. * front-end: added import and export functionality for user defined queries. * front-end: added new keywords and functions to the aql-editor theme * front-end: applied tile-style to the graph view * front-end: now using the new graph api including multi-collection support * front-end: foxx apps are now deleteable * front-end: foxx apps are now installable and updateable through github, if github is their origin. * front-end: added foxx app version control. Multiple versions of a single foxx app are now installable and easy to manage and are also arranged in groups. * front-end: the user-set filter of a collection is now stored until the user navigates to another collection. * front-end: fetching and filtering of documents, statistics, and query operations are now handled with asynchronous ajax calls. * front-end: added progress indicator if the front-end is waiting for a server operation. * front-end: fixed wrong count of documents in the documents view of a collection. * front-end: fixed unexpected styling of the manage db view and navigation. * front-end: fixed wrong handling of select fields in a modal view. * front-end: fixed wrong positioning of some tooltips. * automatically call `toJSON` function of JavaScript objects (if present) when serializing them into database documents. This change allows storing JavaScript date objects in the database in a sensible manner. -- ArangoDB Maintainer Mon, 22 Sep 2014 20:30:35 +0200 arangodb (2.2.3-1.1) stable; urgency=low * Changed to Version 2.2.3 * added `around` for Foxx controller * added `type` option for HTTP API `GET /_api/document?collection=...` This allows controlling the type of results to be returned. By default, paths to documents will be returned, e.g. [ `/_api/document/test/mykey1`, `/_api/document/test/mykey2`, ... ] To return a list of document ids instead of paths, the `type` URL parameter can be set to `id`: [ `test/mykey1`, `test/mykey2`, ... ] To return a list of document keys only, the `type` URL parameter can be set to `key`: [ `mykey1`, `mykey2`, ... ] * properly capitalize HTTP response header field names in case the `x-arango-async` HTTP header was used in a request. * fixed several documentation issues * speedup for several general-graph functions, AQL functions starting with `GRAPH_` and traversals -- ArangoDB Maintainer Tue, 02 Sep 2014 11:30:26 +0200 arangodb (2.2.3r1-1.1) stable; urgency=low * Changed to Version 2.2.3-rc1 * added `type` option for HTTP API `GET /_api/document?collection=...` This allows controlling the type of results to be returned. By default, paths to documents will be returned, e.g. [ `/_api/document/test/mykey1`, `/_api/document/test/mykey2`, ... ] To return a list of document ids instead of paths, the `type` URL parameter can be set to `id`: [ `test/mykey1`, `test/mykey2`, ... ] To return a list of document keys only, the `type` URL parameter can be set to `key`: [ `mykey1`, `mykey2`, ... ] * properly capitalize HTTP response header field names in case the `x-arango-async` HTTP header was used in a request. * fixed several documentation issues * speedup for several general-graph functions, AQL functions starting with `GRAPH_` and traversals -- ArangoDB Maintainer Mon, 01 Sep 2014 15:58:14 +0200 arangodb (2.2.2-1.1) stable; urgency=low * Changed to Version 2.2.2 * allow storing non-reserved attribute names starting with an underscore Previous versions of ArangoDB parsed away all attribute names that started with an underscore (e.g. `_test', '_foo', `_bar`) on all levels of a document (root level and sub-attribute levels). While this behavior was documented, it was unintuitive and prevented storing documents inside other documents, e.g.: { "_key" : "foo", "_type" : "mydoc", "references" : [ { "_key" : "something", "_rev" : "...", "value" : 1 }, { "_key" : "something else", "_rev" : "...", "value" : 2 } ] } In the above example, previous versions of ArangoDB removed all attributes and sub-attributes that started with underscores, meaning the embedded documents would lose some of their attributes. 2.2.2 should preserve such attributes, and will also allow storing user-defined attribute names on the top-level even if they start with underscores (such as `_type` in the above example). * fix conversion of JavaScript String, Number and Boolean objects to JSON. Objects created in JavaScript using `new Number(...)`, `new String(...)`, or `new Boolean(...)` were not converted to JSON correctly. * fixed a race condition on task registration (i.e. `require("org/arangodb/tasks").register()`) this race condition led to undefined behavior when a just-created task with no offset and no period was instantly executed and deleted by the task scheduler, before the `register` function returned to the caller. * changed run-tests.sh to execute all suitable tests. * switch to new version of gyp * fixed upgrade button -- ArangoDB Maintainer Fri, 08 Aug 2014 12:26:37 +0200 arangodb (2.2.2r1-1.1) stable; urgency=low * Changed to Version 2.2.2-rc1 * fixed a race condition on task registration (i.e. `require("org/arangodb/tasks").register()`) this race condition led to undefined behavior when a just-created task with no offset and no period was instantly executed and deleted by the task scheduler, before the `register` function returned to the caller. * changed run-tests.sh to execute all suitable tests. * switch to new version of gyp * fixed upgrade button -- ArangoDB Maintainer Wed, 06 Aug 2014 11:21:54 +0200 arangodb (2.2.1-1.1) stable; urgency=low * Changed to Version 2.2.1 * fixed issue with --check-version: when creating a new database the check failed * issue #947 Foxx applicationContext missing some properties * added startup option `--wal.suppress-shape-information` Setting this option to `true` will reduce memory and disk space usage and require less CPU time when modifying documents or edges. It should therefore be turned on for standalone ArangoDB servers. However, for servers that are used as replication masters, setting this option to `true` will effectively disable the usage of the write-ahead log for replication, so it should be set to `false` for any replication master servers. The default value for this option is `false`. * added optional `ttl` attribute to specify result cursor expiration for HTTP API method `POST /_api/cursor` The `ttl` attribute can be used to prevent cursor results from timing out too early. * (reported by Christian Neubauer): The problem was that in Google's V8, signed and unsigned chars are not always declared cleanly. so we need to force v8 to compile with forced signed chars which is done by the Flag: -fsigned-char at least it is enough to follow the instructions of compiling arango on rasperry and add "CFLAGS='-fsigned-char'" to the make command of V8 and remove the armv7=0 * Fixed a bug with the replication client. In the case of single document transactions the collection was not write locked. -- ArangoDB Maintainer Thu, 24 Jul 2014 12:22:18 +0200 arangodb (2.2.1r1-1.1) stable; urgency=low * Changed to Version 2.2.1-rc1 * fixed issue with --check-version: when creating a new database the check failed * issue #947 Foxx applicationContext missing some properties * added startup option `--wal.suppress-shape-information` Setting this option to `true` will reduce memory and disk space usage and require less CPU time when modifying documents or edges. It should therefore be turned on for standalone ArangoDB servers. However, for servers that are used as replication masters, setting this option to `true` will effectively disable the usage of the write-ahead log for replication, so it should be set to `false` for any replication master servers. The default value for this option is `false`. * added optional `ttl` attribute to specify result cursor expiration for HTTP API method `POST /_api/cursor` The `ttl` attribute can be used to prevent cursor results from timing out too early. * (reported by Christian Neubauer): The problem was that in Google's V8, signed and unsigned chars are not always declared cleanly. so we need to force v8 to compile with forced signed chars which is done by the Flag: -fsigned-char at least it is enough to follow the instructions of compiling arango on rasperry and add "CFLAGS='-fsigned-char'" to the make command of V8 and remove the armv7=0 * Fixed a bug with the replication client. In the case of single document transactions the collection was not write locked. -- ArangoDB Maintainer Wed, 23 Jul 2014 18:37:33 +0200 arangodb (2.2.0-1.1) stable; urgency=low * Changed to Version 2.2.0 * The replication methods `logger.start`, `logger.stop` and `logger.properties` are no-ops in ArangoDB 2.2 as there is no separate replication logger anymore. Data changes are logged into the write-ahead log in ArangoDB 2.2, and not separately by the replication logger. The replication logger object is still there in ArangoDB 2.2 to ensure backwards-compatibility, however, logging cannot be started, stopped or configured anymore. Using any of these methods will do nothing. This also affects the following HTTP API methods: - `PUT /_api/replication/logger-start` - `PUT /_api/replication/logger-stop` - `GET /_api/replication/logger-config` - `PUT /_api/replication/logger-config` Using any of these methods is discouraged from now on as they will be removed in future versions of ArangoDB. * INCOMPATIBLE CHANGE: replication of transactions has changed. Previously, transactions were logged on a master in one big block and shipped to a slave in one block, too. Now transactions will be logged and replicated as separate entries, allowing transactions to be bigger and also ensure replication progress. This change also affects the behavior of the `stop` method of the replication applier. If the replication applier is now stopped manually using the `stop` method and later restarted using the `start` method, any transactions that were unfinished at the point of stopping will be aborted on a slave, even if they later commit on the master. In ArangoDB 2.2, stopping the replication applier manually should be avoided unless the goal is to stop replication permanently or to do a full resync with the master anyway. If the replication applier still must be stopped, it should be made sure that the slave has fetched and applied all pending operations from a master, and that no extra transactions are started on the master before the `stop` command on the slave is executed. Replication of transactions in ArangoDB 2.2 might also lock the involved collections on the slave while a transaction is either committed or aborted on the master and the change has been replicated to the slave. This change in behavior may be important for slave servers that are used for read-scaling. In order to avoid long lasting collection locks on the slave, transactions should be kept small. The `_replication` system collection is not used anymore in ArangoDB 2.2 and its usage is discouraged. * INCOMPATIBLE CHANGE: the figures reported by the `collection.figures` method now only reflect documents and data contained in the journals and datafiles of collections. Documents or deletions contained only in the write-ahead log will not influence collection figures until the write-ahead log garbage collection kicks in. The figures for a collection might therefore underreport the total resource usage of a collection. Additionally, the attributes `lastTick` and `uncollectedLogfileEntries` have been added to the result of the `figures` operation and the HTTP API method `PUT /_api/collection/figures` * added `insert` method as an alias for `save`. Documents can now be inserted into a collection using either method: db.test.save({ foo: "bar" }); db.test.insert({ foo: "bar" }); * added support for data-modification AQL queries * added AQL keywords `INSERT`, `UPDATE`, `REPLACE` and `REMOVE` (and `WITH`) to support data-modification AQL queries. Unquoted usage of these keywords for attribute names in AQL queries will likely fail in ArangoDB 2.2. If any such attribute name needs to be used in a query, it should be enclosed in backticks to indicate the usage of a literal attribute name. For example, the following query will fail in ArangoDB 2.2 with a parse error: FOR i IN foo RETURN i.remove and needs to be rewritten like this: FOR i IN foo RETURN i.`remove` * disallow storing of JavaScript objects that contain JavaScript native objects of type `Date`, `Function`, `RegExp` or `External`, e.g. db.test.save({ foo: /bar/ }); db.test.save({ foo: new Date() }); will now print Error: cannot be converted into JSON shape: could not shape document Previously, objects of these types were silently converted into an empty object (i.e. `{ }`). To store such objects in a collection, explicitly convert them into strings like this: db.test.save({ foo: String(/bar/) }); db.test.save({ foo: String(new Date()) }); * The replication methods `logger.start`, `logger.stop` and `logger.properties` are no-ops in ArangoDB 2.2 as there is no separate replication logger anymore. Data changes are logged into the write-ahead log in ArangoDB 2.2, and not separately by the replication logger. The replication logger object is still there in ArangoDB 2.2 to ensure backwards-compatibility, however, logging cannot be started, stopped or configured anymore. Using any of these methods will do nothing. This also affects the following HTTP API methods: - `PUT /_api/replication/logger-start` - `PUT /_api/replication/logger-stop` - `GET /_api/replication/logger-config` - `PUT /_api/replication/logger-config` Using any of these methods is discouraged from now on as they will be removed in future versions of ArangoDB. * INCOMPATIBLE CHANGE: replication of transactions has changed. Previously, transactions were logged on a master in one big block and shipped to a slave in one block, too. Now transactions will be logged and replicated as separate entries, allowing transactions to be bigger and also ensure replication progress. This change also affects the behavior of the `stop` method of the replication applier. If the replication applier is now stopped manually using the `stop` method and later restarted using the `start` method, any transactions that were unfinished at the point of stopping will be aborted on a slave, even if they later commit on the master. In ArangoDB 2.2, stopping the replication applier manually should be avoided unless the goal is to stop replication permanently or to do a full resync with the master anyway. If the replication applier still must be stopped, it should be made sure that the slave has fetched and applied all pending operations from a master, and that no extra transactions are started on the master before the `stop` command on the slave is executed. Replication of transactions in ArangoDB 2.2 might also lock the involved collections on the slave while a transaction is either committed or aborted on the master and the change has been replicated to the slave. This change in behavior may be important for slave servers that are used for read-scaling. In order to avoid long lasting collection locks on the slave, transactions should be kept small. The `_replication` system collection is not used anymore in ArangoDB 2.2 and its usage is discouraged. * INCOMPATIBLE CHANGE: the figures reported by the `collection.figures` method now only reflect documents and data contained in the journals and datafiles of collections. Documents or deletions contained only in the write-ahead log will not influence collection figures until the write-ahead log garbage collection kicks in. The figures for a collection might therefore underreport the total resource usage of a collection. Additionally, the attributes `lastTick` and `uncollectedLogfileEntries` have been added to the result of the `figures` operation and the HTTP API method `PUT /_api/collection/figures` * added `insert` method as an alias for `save`. Documents can now be inserted into a collection using either method: db.test.save({ foo: "bar" }); db.test.insert({ foo: "bar" }); * added support for data-modification AQL queries * added AQL keywords `INSERT`, `UPDATE`, `REPLACE` and `REMOVE` (and `WITH`) to support data-modification AQL queries. Unquoted usage of these keywords for attribute names in AQL queries will likely fail in ArangoDB 2.2. If any such attribute name needs to be used in a query, it should be enclosed in backticks to indicate the usage of a literal attribute name. For example, the following query will fail in ArangoDB 2.2 with a parse error: FOR i IN foo RETURN i.remove and needs to be rewritten like this: FOR i IN foo RETURN i.`remove` * disallow storing of JavaScript objects that contain JavaScript native objects of type `Date`, `Function`, `RegExp` or `External`, e.g. db.test.save({ foo: /bar/ }); db.test.save({ foo: new Date() }); will now print Error: cannot be converted into JSON shape: could not shape document Previously, objects of these types were silently converted into an empty object (i.e. `{ }`). To store such objects in a collection, explicitly convert them into strings like this: db.test.save({ foo: String(/bar/) }); db.test.save({ foo: String(new Date()) }); * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` This option was used for debugging only. * removed startup option `--database.force-sync-properties` This option is now superfluous as collection properties are now stored in the write-ahead log. * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the journals or datafiles of collections, allowing the server to remove older write-ahead log logfiles. Figures of collections will be updated when data are moved from the write-ahead log into the journals or datafiles of collections. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions are required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, that required all transaction data to fit into RAM. The `_trx` system collection is not used anymore in ArangoDB 2.2 and its usage is discouraged. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. * fixed a bug in arangodump which got the collection name in _from and _to attributes of edges wrong (all were "_unknown") * fixed a bug in arangorestore which did not recognise wrong _from and _to attributes of edges * improved error detection and reporting in arangorestore -- ArangoDB Maintainer Fri, 11 Jul 2014 12:28:20 +0200 arangodb (2.2.0b3-1.1) stable; urgency=low * Changed to Version 2.2.0-beta3 * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Tue, 01 Jul 2014 18:30:19 +0200 arangodb (2.2.0b2-1.1) stable; urgency=low * Changed to Version 2.2.0-beta2 * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Tue, 01 Jul 2014 09:51:22 +0200 arangodb (2.2.0b1-1.1) stable; urgency=low * Changed to Version 2.2.0-beta1 * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Sat, 28 Jun 2014 10:34:22 +0200 arangodb (2.2.0a6-1.1) stable; urgency=low * Changed to Version 2.2.0-alpha6 * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Fri, 27 Jun 2014 11:33:12 +0200 arangodb (2.2.0a4-1.1) stable; urgency=low * Changed to Version 2.2.0-alpha4 * honor startup option `--server.disable-statistics` when deciding whether or not to start periodic statistics collection jobs Previously, the statistics collection jobs were started even if the server was started with the `--server.disable-statistics` flag being set to `true` * removed startup option `--random.no-seed` This option had no effect in previous versions of ArangoDB and was thus removed. * removed startup option `--database.remove-on-drop` * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Wed, 25 Jun 2014 23:56:02 +0200 arangodb (2.2.0a2-1.1) stable; urgency=low * Changed to Version 2.2.0-alpha2 * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Mon, 23 Jun 2014 16:43:29 +0200 arangodb (2.2.0a1-1.1) stable; urgency=low * Changed to Version 2.2.0-alpha1 * introduced write-ahead log All write operations in an ArangoDB server instance are automatically logged to the server's write-ahead log. The write-ahead log is a set of append-only logfiles, and it is used in case of a crash recovery and for replication. Data from the write-ahead log will eventually be moved into the datafiles of collections, allowing the server to remove older write-ahead log logfiles. Cross-collection transactions in ArangoDB should benefit considerably by this change, as less writes than in previous versions is required to ensure the data of multiple collections are atomcially and durably committed. All data-modifying operations inside transactions (insert, update, remove) will write their operations into the write-ahead log directly, making transactions with multiple operations also require less physical memory than in previous versions of ArangoDB, where most parts of transactions were handled in RAM first. The data in the write-ahead log can also be used in the replication context. The `_replication` collection that was used in previous versions of ArangoDB to store all changes on the server is not used anymore in ArangoDB 2.2. Instead, slaves can read from a master's write-ahead log to get informed about most recent changes. This removes the need to store data-modifying operations in both the actual place and the `_replication` collection. Note: the replication from the write-ahead log is still in development. * removed startup option `--server.disable-replication-logger` This option is superfluous in ArangoDB 2.2. There is no dedicated replication logger in ArangoDB 2.2. There is now always the write-ahead log, and it is also used as the server's replication log. Specifying the startup option `--server.disable-replication-logger` will do nothing in ArangoDB 2.2, but the option should not be used anymore as it might be removed in a future version. * changed behavior of replication logger There is no dedicated replication logger in ArangoDB 2.2 as there is the write-ahead log now. The existing APIs for starting and stopping the replication logger still exist in ArangoDB 2.2 for downwards-compatibility, but calling the start or stop operations are no-ops in ArangoDB 2.2. When querying the replication logger status via the API, the server will always report that the replication logger is running. Configuring the replication logger is a no-op in ArangoDB 2.2, too. Changing the replication logger configuration has no effect. Instead, the write-ahead log configuration can be changed. * removed MRuby integration for arangod ArangoDB had an experimental MRuby integration in some of the publish builds. This wasn't continuously developed, and so it has been removed in ArangoDB 2.2. This change has led to the following startup options being superfluous: - `--ruby.gc-interval` - `--ruby.action-directory` - `--ruby.modules-path` - `--ruby.startup-directory` Specifying these startup options will do nothing in ArangoDB 2.2, but the options should be avoided from now on as they might be removed in future versions. * reclaim index memory when last document in collection is deleted Previously, deleting documents from a collection did not lead to index sizes being reduced. Instead, the already allocated index memory was re-used when a collection was refilled. Now, index memory for primary indexes and hash indexes is reclaimed instantly when the last document from a collection is removed. * inlined and optimized functions in hash indexes * added AQL TRANSLATE function This function can be used to perform lookups from static lists, e.g. LET countryNames = { US: "United States", UK: "United Kingdom", FR: "France" } RETURN TRANSLATE("FR", countryNames) * fixed datafile debugger * fixed check-version for empty directory * moved try/catch block to the top of routing chain * added mountedApp function for foxx-manager * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard * specialized primary index implementation to allow faster hash table rebuilding and reduce lookups in datafiles for the actual value of `_key`. * issue #862: added `--overwrite` option to arangoimp * removed number of property lookups for documents during AQL queries that access documents * prevent buffering of long print results in arangosh's and arangod's print command this change will emit buffered intermediate print results and discard the output buffer to quickly deliver print results to the user, and to prevent constructing very large buffers for large results * removed sorting of attribute names for use in a collection's shaper sorting attribute names was done on document insert to keep attributes of a collection in sorted order for faster comparisons. The sort order of attributes was only used in one particular and unlikely case, so it was removed. Collections with many different attribute names should benefit from this change by faster inserts and slightly less memory usage. -- ArangoDB Maintainer Mon, 23 Jun 2014 11:46:12 +0200 arangodb (2.1.2-1.1) stable; urgency=low * Changed to Version 2.1.2 * fixed check-version for empty directory * moved try/catch block to the top of routing chain -- ArangoDB Maintainer Sun, 15 Jun 2014 16:05:00 +0200 arangodb (2.1.1-1.1) stable; urgency=low * Changed to Version 2.1.1 * fixed random generation under MacOSX * fixed issue #883: arango 2.1 - when starting multi-machine cluster, UI web does not change to cluster overview * fixed dfdb: should not start any other V8 threads * cleanup of version-check, added module org/arangodb/database-version, added --check-version option * fixed issue #881: [2.1.0] Bombarded (every 10 sec or so) with "WARNING format string is corrupt" when in non-system DB Dashboard -- ArangoDB Maintainer Fri, 06 Jun 2014 18:41:30 +0200 -- ArangoDB Maintainer Sun, 01 Jun 2014 22:10:48 +0200 arangodb (2.1.0-1.1) stable; urgency=low * Changed to Version 2.1.0 * implemented upgrade procedure for clusters * fixed communication issue with agency which prevented reconnect after an agent failure * fixed cluster dashboard in the case that one but not all servers in the cluster are down * fixed a bug with coordinators creating local database objects in the wrong order (_system needs to be done successfully first), which lead to a coordinator on strike * improved cluster dashboard -- ArangoDB Maintainer Thu, 29 May 2014 11:01:03 +0200 arangodb (2.1.0r2-1.1) stable; urgency=low * Changed to Version 2.1.0-rc2 * fixed issue #864: Inconsistent behavior of AQL REVERSE(list) function -- ArangoDB Maintainer Mon, 26 May 2014 00:48:13 +0200 arangodb (2.1.0r1-1.1) stable; urgency=low * Changed to Version 2.1.0-rc1 * added server-side periodic task management functions: - require("org/arangodb/tasks").register(): registers a periodic task - require("org/arangodb/tasks").unregister(): unregisters and removes a periodic task - require("org/arangodb/tasks").get(): retrieves a specific tasks or all existing tasks the previous undocumented function `internal.definePeriodic` is now deprecated and will be removed in a future release. * decrease the size of some seldomly used system collections on creation. This will make these collections use less disk space and mapped memory. * added AQL date functions * added AQL FLATTEN() and FLATTEN_RECURSIVE() list functions * added index memory statistics to `db..figures()` function The `figures` function will now return a sub-document `indexes`, which lists the number of indexes in the `count` sub-attribute, and the total memory usage of the indexes in bytes in the `size` sub-attribute. * added AQL CURRENT_DATABASE() function This function returns the current database's name. * added AQL CURRENT_USER() function This function returns the current user from an AQL query. The current user is the username that was specified in the `Authorization` HTTP header of the request. If authentication is turned off or the query was executed outside a request context, the function will return `null`. * fixed issue #796: Searching with newline chars broken? fixed slightly different handling of backslash escape characters in a few AQL functions. Now handling of escape sequences should be consistent, and searching for newline characters should work the same everywhere * added OpenSSL version check for configure It will report all OpenSSL versions < 1.0.1g as being too old. `configure` will only complain about an outdated OpenSSL version but not stop. * require C++ compiler support (requires g++ 4.8, clang++ 3.4 or Visual Studio 13) * less string copying returning JSONified documents from ArangoDB, e.g. via HTTP GET `/_api/document//` * issue #798: Lower case http headers from arango This change allows returning capitalized HTTP headers, e.g. `Content-Length` instead of `content-length`. The HTTP spec says that headers are case-insensitive, but in fact several clients rely on a specific case in response headers. This change will capitalize HTTP headers if the `X-Arango-Version` request header is sent by the client and contains a value of at least `20100` (for version 2.1). The default value for the compatibility can also be set at server start, using the `--server.default-api-compatibility` option. * simplified usage of `db._createStatement()` Previously, the function could not be called with a query string parameter as follows: db._createStatement(queryString); Calling it as above resulted in an error because the function expected an object as its parameter. From now on, it's possible to call the function with just the query string. * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * use a new data structure for the edge index of an edge collection. This improves the performance for the creation of the edge index and in particular speeds up removal of edges in graphs. Note however that this change might change the order in which edges starting at or ending in a vertex are returned. However, this order was never guaranteed anyway and it is not sensible to guarantee any particular order. * provide a size hint to edge and hash indexes when initially filling them this will lead to less re-allocations when populating these indexes this may speed up building indexes when opening an existing collection * don't requeue identical context methods in V8 threads in case a method is already registered * removed arangod command line option `--database.remove-on-compacted` * export the sort attribute for graph traversals to the HTTP interface * add support for arangodump/arangorestore for clusters -- ArangoDB Maintainer Mon, 12 May 2014 19:29:58 +0200 arangodb (2.1.0a9-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha9 * added server-side periodic task management functions: - require("org/arangodb/tasks").register(): registers a periodic task - require("org/arangodb/tasks").unregister(): unregisters and removes a periodic task - require("org/arangodb/tasks").get(): retrieves a specific tasks or all existing tasks the previous undocumented function `internal.definePeriodic` is now deprecated and will be removed in a future release. * decrease the size of some seldomly used system collections on creation. This will make these collections use less disk space and mapped memory. * added AQL date functions * added AQL FLATTEN() and FLATTEN_RECURSIVE() list functions * added index memory statistics to `db..figures()` function The `figures` function will now return a sub-document `indexes`, which lists the number of indexes in the `count` sub-attribute, and the total memory usage of the indexes in bytes in the `size` sub-attribute. * added AQL CURRENT_DATABASE() function This function returns the current database's name. * added AQL CURRENT_USER() function This function returns the current user from an AQL query. The current user is the username that was specified in the `Authorization` HTTP header of the request. If authentication is turned off or the query was executed outside a request context, the function will return `null`. * fixed issue #796: Searching with newline chars broken? fixed slightly different handling of backslash escape characters in a few AQL functions. Now handling of escape sequences should be consistent, and searching for newline characters should work the same everywhere * added OpenSSL version check for configure It will report all OpenSSL versions < 1.0.1g as being too old. `configure` will only complain about an outdated OpenSSL version but not stop. * require C++ compiler support (requires g++ 4.8, clang++ 3.4 or Visual Studio 13) * less string copying returning JSONified documents from ArangoDB, e.g. via HTTP GET `/_api/document//` * issue #798: Lower case http headers from arango This change allows returning capitalized HTTP headers, e.g. `Content-Length` instead of `content-length`. The HTTP spec says that headers are case-insensitive, but in fact several clients rely on a specific case in response headers. This change will capitalize HTTP headers if the `X-Arango-Version` request header is sent by the client and contains a value of at least `20100` (for version 2.1). The default value for the compatibility can also be set at server start, using the `--server.default-api-compatibility` option. * simplified usage of `db._createStatement()` Previously, the function could not be called with a query string parameter as follows: db._createStatement(queryString); Calling it as above resulted in an error because the function expected an object as its parameter. From now on, it's possible to call the function with just the query string. * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * use a new data structure for the edge index of an edge collection. This improves the performance for the creation of the edge index and in particular speeds up removal of edges in graphs. Note however that this change might change the order in which edges starting at or ending in a vertex are returned. However, this order was never guaranteed anyway and it is not sensible to guarantee any particular order. * provide a size hint to edge and hash indexes when initially filling them this will lead to less re-allocations when populating these indexes this may speed up building indexes when opening an existing collection * don't requeue identical context methods in V8 threads in case a method is already registered * removed arangod command line option `--database.remove-on-compacted` * export the sort attribute for graph traversals to the HTTP interface * add support for arangodump/arangorestore for clusters -- ArangoDB Maintainer Sun, 11 May 2014 01:13:36 +0200 arangodb (2.1.0a7-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha7 * added server-side periodic task management functions: - require("org/arangodb/tasks").register(): registers a periodic task - require("org/arangodb/tasks").unregister(): unregisters and removes a periodic task - require("org/arangodb/tasks").get(): retrieves a specific tasks or all existing tasks the previous undocumented function `internal.definePeriodic` is now deprecated and will be removed in a future release. * decrease the size of some seldomly used system collections on creation. This will make these collections use less disk space and mapped memory. * added AQL date functions * added AQL FLATTEN() and FLATTEN_RECURSIVE() list functions * added index memory statistics to `db..figures()` function The `figures` function will now return a sub-document `indexes`, which lists the number of indexes in the `count` sub-attribute, and the total memory usage of the indexes in bytes in the `size` sub-attribute. * added AQL CURRENT_DATABASE() function This function returns the current database's name. * added AQL CURRENT_USER() function This function returns the current user from an AQL query. The current user is the username that was specified in the `Authorization` HTTP header of the request. If authentication is turned off or the query was executed outside a request context, the function will return `null`. * fixed issue #796: Searching with newline chars broken? fixed slightly different handling of backslash escape characters in a few AQL functions. Now handling of escape sequences should be consistent, and searching for newline characters should work the same everywhere * added OpenSSL version check for configure It will report all OpenSSL versions < 1.0.1g as being too old. `configure` will only complain about an outdated OpenSSL version but not stop. * require C++ compiler support (requires g++ 4.8, clang++ 3.4 or Visual Studio 13) * less string copying returning JSONified documents from ArangoDB, e.g. via HTTP GET `/_api/document//` * issue #798: Lower case http headers from arango This change allows returning capitalized HTTP headers, e.g. `Content-Length` instead of `content-length`. The HTTP spec says that headers are case-insensitive, but in fact several clients rely on a specific case in response headers. This change will capitalize HTTP headers if the `X-Arango-Version` request header is sent by the client and contains a value of at least `20100` (for version 2.1). The default value for the compatibility can also be set at server start, using the `--server.default-api-compatibility` option. * simplified usage of `db._createStatement()` Previously, the function could not be called with a query string parameter as follows: db._createStatement(queryString); Calling it as above resulted in an error because the function expected an object as its parameter. From now on, it's possible to call the function with just the query string. * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * use a new data structure for the edge index of an edge collection. This improves the performance for the creation of the edge index and in particular speeds up removal of edges in graphs. Note however that this change might change the order in which edges starting at or ending in a vertex are returned. However, this order was never guaranteed anyway and it is not sensible to guarantee any particular order. * provide a size hint to edge and hash indexes when initially filling them this will lead to less re-allocations when populating these indexes this may speed up building indexes when opening an existing collection * don't requeue identical context methods in V8 threads in case a method is already registered * removed arangod command line option `--database.remove-on-compacted` * export the sort attribute for graph traversals to the HTTP interface * add support for arangodump/arangorestore for clusters -- ArangoDB Maintainer Sat, 10 May 2014 20:05:38 +0200 arangodb (2.1.0a6-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha6 * added server-side periodic task management functions: - require("org/arangodb/tasks").register(): registers a periodic task - require("org/arangodb/tasks").unregister(): unregisters and removes a periodic task - require("org/arangodb/tasks").get(): retrieves a specific tasks or all existing tasks the previous undocumented function `internal.definePeriodic` is now deprecated and will be removed in a future release. * decrease the size of some seldomly used system collections on creation. This will make these collections use less disk space and mapped memory. * added AQL date functions * added AQL FLATTEN() and FLATTEN_RECURSIVE() list functions * added index memory statistics to `db..figures()` function The `figures` function will now return a sub-document `indexes`, which lists the number of indexes in the `count` sub-attribute, and the total memory usage of the indexes in bytes in the `size` sub-attribute. * added AQL CURRENT_DATABASE() function This function returns the current database's name. * added AQL CURRENT_USER() function This function returns the current user from an AQL query. The current user is the username that was specified in the `Authorization` HTTP header of the request. If authentication is turned off or the query was executed outside a request context, the function will return `null`. * fixed issue #796: Searching with newline chars broken? fixed slightly different handling of backslash escape characters in a few AQL functions. Now handling of escape sequences should be consistent, and searching for newline characters should work the same everywhere * added OpenSSL version check for configure It will report all OpenSSL versions < 1.0.1g as being too old. `configure` will only complain about an outdated OpenSSL version but not stop. * require C++ compiler support (requires g++ 4.8, clang++ 3.4 or Visual Studio 13) * less string copying returning JSONified documents from ArangoDB, e.g. via HTTP GET `/_api/document//` * issue #798: Lower case http headers from arango This change allows returning capitalized HTTP headers, e.g. `Content-Length` instead of `content-length`. The HTTP spec says that headers are case-insensitive, but in fact several clients rely on a specific case in response headers. This change will capitalize HTTP headers if the `X-Arango-Version` request header is sent by the client and contains a value of at least `20100` (for version 2.1). The default value for the compatibility can also be set at server start, using the `--server.default-api-compatibility` option. * simplified usage of `db._createStatement()` Previously, the function could not be called with a query string parameter as follows: db._createStatement(queryString); Calling it as above resulted in an error because the function expected an object as its parameter. From now on, it's possible to call the function with just the query string. * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * use a new data structure for the edge index of an edge collection. This improves the performance for the creation of the edge index and in particular speeds up removal of edges in graphs. Note however that this change might change the order in which edges starting at or ending in a vertex are returned. However, this order was never guaranteed anyway and it is not sensible to guarantee any particular order. * provide a size hint to edge and hash indexes when initially filling them this will lead to less re-allocations when populating these indexes this may speed up building indexes when opening an existing collection * don't requeue identical context methods in V8 threads in case a method is already registered * removed arangod command line option `--database.remove-on-compacted` * export the sort attribute for graph traversals to the HTTP interface * add support for arangodump/arangorestore for clusters -- ArangoDB Maintainer Sat, 10 May 2014 19:37:47 +0200 arangodb (2.1.0a4-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha4 * added server-side periodic task management functions: - require("org/arangodb/tasks").register(): registers a periodic task - require("org/arangodb/tasks").unregister(): unregisters and removes a periodic task - require("org/arangodb/tasks").get(): retrieves a specific tasks or all existing tasks the previous undocumented function `internal.definePeriodic` is now deprecated and will be removed in a future release. * decrease the size of some seldomly used system collections on creation. This will make these collections use less disk space and mapped memory. * added AQL date functions * added AQL FLATTEN() and FLATTEN_RECURSIVE() list functions * added index memory statistics to `db..figures()` function The `figures` function will now return a sub-document `indexes`, which lists the number of indexes in the `count` sub-attribute, and the total memory usage of the indexes in bytes in the `size` sub-attribute. * added AQL CURRENT_DATABASE() function This function returns the current database's name. * added AQL CURRENT_USER() function This function returns the current user from an AQL query. The current user is the username that was specified in the `Authorization` HTTP header of the request. If authentication is turned off or the query was executed outside a request context, the function will return `null`. * fixed issue #796: Searching with newline chars broken? fixed slightly different handling of backslash escape characters in a few AQL functions. Now handling of escape sequences should be consistent, and searching for newline characters should work the same everywhere * added OpenSSL version check for configure It will report all OpenSSL versions < 1.0.1g as being too old. `configure` will only complain about an outdated OpenSSL version but not stop. * require C++ compiler support (requires g++ 4.8, clang++ 3.4 or Visual Studio 13) * less string copying returning JSONified documents from ArangoDB, e.g. via HTTP GET `/_api/document//` * issue #798: Lower case http headers from arango This change allows returning capitalized HTTP headers, e.g. `Content-Length` instead of `content-length`. The HTTP spec says that headers are case-insensitive, but in fact several clients rely on a specific case in response headers. This change will capitalize HTTP headers if the `X-Arango-Version` request header is sent by the client and contains a value of at least `20100` (for version 2.1). The default value for the compatibility can also be set at server start, using the `--server.default-api-compatibility` option. * simplified usage of `db._createStatement()` Previously, the function could not be called with a query string parameter as follows: db._createStatement(queryString); Calling it as above resulted in an error because the function expected an object as its parameter. From now on, it's possible to call the function with just the query string. * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * use a new data structure for the edge index of an edge collection. This improves the performance for the creation of the edge index and in particular speeds up removal of edges in graphs. Note however that this change might change the order in which edges starting at or ending in a vertex are returned. However, this order was never guaranteed anyway and it is not sensible to guarantee any particular order. * provide a size hint to edge and hash indexes when initially filling them this will lead to less re-allocations when populating these indexes this may speed up building indexes when opening an existing collection * don't requeue identical context methods in V8 threads in case a method is already registered * removed arangod command line option `--database.remove-on-compacted` * export the sort attribute for graph traversals to the HTTP interface * add support for arangodump/arangorestore for clusters -- ArangoDB Maintainer Sat, 10 May 2014 15:07:44 +0200 arangodb (2.1.0a3-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha3 * fixed issue #848: db.someEdgeCollection.inEdge does not return correct -- ArangoDB Maintainer Sat, 10 May 2014 11:46:54 +0200 arangodb (2.1.0a3-1.1) stable; urgency=low * Changed to Version 2.1.0-alpha3 * fixed issue #848: db.someEdgeCollection.inEdge does not return correct -- ArangoDB Maintainer Sat, 10 May 2014 11:16:50 +0200 arangodb (2.0.nightly-1.1) stable; urgency=low * Changed to Version 2.0.nightly -- ArangoDB Maintainer Tue, 06 May 2014 01:20:47 +0200 arangodb (2.0.7-1.1) stable; urgency=low * Changed to Version 2.0.7 * issue #839: Foxx Manager missing "unfetch" * fixed a race condition at startup this fixes undefined behavior in case the logger was involved directly at startup, before the logger initialization code was called. This should have occurred only for code that was executed before the invocation of main(), e.g. during ctor calls of statically defined objects. * fixed permission problems under Windows -- ArangoDB Maintainer Mon, 05 May 2014 19:23:11 +0200 arangodb (2.0.6-1.1) stable; urgency=low * Changed to Version 2.0.6 * fixed issue #835: arangosh doesn't show correct database name -- ArangoDB Maintainer Tue, 22 Apr 2014 23:19:09 +0200 arangodb (2.0.5-1.1) stable; urgency=low * Changed to Version 2.0.5 * Fixed a caching problem in IE JS Shell * added cancelation for async jobs * upgraded to new gyp for V8 * new Windows installer -- ArangoDB Maintainer Mon, 21 Apr 2014 17:02:15 +0200 arangodb (2.0.4-1.1) stable; urgency=low * Changed to Version 2.0.4 * fixed cluster authentication front-end issues for Firefox and IE, there are still problems with Chrome -- ArangoDB Maintainer Mon, 14 Apr 2014 20:19:04 +0200 arangodb (2.0.3-1.1) stable; urgency=low * Changed to Version 2.0.3 * fixed AQL optimizer bug * fixed front-end issues * added password change dialog -- ArangoDB Maintainer Sun, 13 Apr 2014 21:33:43 +0200 arangodb (2.0.2-1.1) stable; urgency=low * Changed to Version 2.0.2 * during cluster startup, do not log (somewhat expected) connection errors with log level error, but with log level info * fixed dashboard modals * fixed connection check for cluster planning front end: firefox does not support async:false * document how to persist a cluster plan in order to relaunch an existing cluster later * added REST API method HTTP GET `/_api/job/job-id` to query the status of an async job without potentially fetching it from the list of done jobs * fixed non-intuitive behaviour in jobs API: previously, querying the status of an async job via the API HTTP PUT `/_api/job/job-id` removed a currently executing async job from the list of queryable jobs on the server. Now, when querying the result of an async job that is still executing, the job is kept in the list of queryable jobs so its result can be fetched by a subsequent request. * improve documentation of db._create and explain the rules and limitations following from the choice of shardKeys for sharded collections with more than one shard -- ArangoDB Maintainer Sun, 06 Apr 2014 14:38:55 +0200 arangodb (2.0.1-1.1) stable; urgency=low * Changed to Version 2.0.1 * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * fixed isses in arango-dfdb: the dfdb was not able to unload certain system collections, so these couldn't be inspected with the dfdb sometimes. Additionally, it did not truncate corrupt markers from datafiles under some circumstances * added `changePassword` attribute for users * fixed non-working "save" button in collection edit view of web interface clicking the save button did nothing. one had to press enter in one of the input fields to send modified form data * fixed V8 compile error on MacOS X * prevent `body length: -9223372036854775808` being logged in development mode for some Foxx HTTP responses * fixed several bugs in web interface dashboard * fixed issue #783: coffee script not working in manifest file * fixed issue #781: Cant save current query from AQL editor ui * bumped version in `X-Arango-Version` compatibility header sent by arangosh and other client tools from `1.5` to `2.0`. * fixed startup options for arango-dfdb, added details option for arango-dfdb * fixed display of missing error messages and codes in arangosh * when creating a collection via the web interface, the collection type was always "document", regardless of the user's choice -- ArangoDB Maintainer Mon, 31 Mar 2014 19:52:56 +0200 arangodb (2.0.1r3-1.1) stable; urgency=low * Changed to Version 2.0.1-rc3 * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * fixed isses in arango-dfdb: the dfdb was not able to unload certain system collections, so these couldn't be inspected with the dfdb sometimes. Additionally, it did not truncate corrupt markers from datafiles under some circumstances * added `changePassword` attribute for users * fixed non-working "save" button in collection edit view of web interface clicking the save button did nothing. one had to press enter in one of the input fields to send modified form data * fixed V8 compile error on MacOS X * prevent `body length: -9223372036854775808` being logged in development mode for some Foxx HTTP responses * fixed several bugs in web interface dashboard * fixed issue #783: coffee script not working in manifest file * fixed issue #781: Cant save current query from AQL editor ui * bumped version in `X-Arango-Version` compatibility header sent by arangosh and other client tools from `1.5` to `2.0`. * fixed startup options for arango-dfdb, added details option for arango-dfdb * fixed display of missing error messages and codes in arangosh * when creating a collection via the web interface, the collection type was always "document", regardless of the user's choice -- ArangoDB Maintainer Mon, 31 Mar 2014 10:58:07 +0200 arangodb (2.0.1r2-1.1) stable; urgency=low * Changed to Version 2.0.1-rc2 * make ArangoDB not send back a `WWW-Authenticate` header to a client in case the client sends the `X-Omit-WWW-Authenticate` HTTP header. This is done to prevent browsers from showing their built-in HTTP authentication dialog for AJAX requests that require authentication. ArangoDB will still return an HTTP 401 (Unauthorized) if the request doesn't contain valid credentials, but it will omit the `WWW-Authenticate` header, allowing clients to bypass the browser's authentication dialog. * fixed isses in arango-dfdb: the dfdb was not able to unload certain system collections, so these couldn't be inspected with the dfdb sometimes. Additionally, it did not truncate corrupt markers from datafiles under some circumstances * added `changePassword` attribute for users * fixed non-working "save" button in collection edit view of web interface clicking the save button did nothing. one had to press enter in one of the input fields to send modified form data * fixed V8 compile error on MacOS X * prevent `body length: -9223372036854775808` being logged in development mode for some Foxx HTTP responses * fixed several bugs in web interface dashboard * fixed issue #783: coffee script not working in manifest file * fixed issue #781: Cant save current query from AQL editor ui * bumped version in `X-Arango-Version` compatibility header sent by arangosh and other client tools from `1.5` to `2.0`. * fixed startup options for arango-dfdb, added details option for arango-dfdb * fixed display of missing error messages and codes in arangosh * when creating a collection via the web interface, the collection type was always "document", regardless of the user's choice -- ArangoDB Maintainer Fri, 28 Mar 2014 10:30:40 +0100 arangodb (2.0.0-1.1) stable; urgency=low * Changed to Version 2.0.0 * first 2.0 release -- ArangoDB Maintainer Mon, 10 Mar 2014 16:48:11 +0100 arangodb (2.0.0r2-1.1) stable; urgency=low * Changed to Version 2.0.0-rc2 * fixed cluster authorization -- ArangoDB Maintainer Fri, 07 Mar 2014 14:08:21 +0100 arangodb (2.0.0r1-1.1) stable; urgency=low * Changed to Version 2.0.0-rc1 * added sharding :-) more detailed documentation on the sharding and cluster features can be found in the user manual, section **Sharding** * INCOMPATIBLE CHANGE: using complex values in AQL filter conditions with operators other than equality (e.g. >=, >, <=, <) will disable usage of skiplist indexes for filter evaluation. For example, the following queries will be affected by change: FOR doc IN docs FILTER doc.value < { foo: "bar" } RETURN doc FOR doc IN docs FILTER doc.value >= [ 1, 2, 3 ] RETURN doc The following queries will not be affected by the change: FOR doc IN docs FILTER doc.value == 1 RETURN doc FOR doc IN docs FILTER doc.value == "foo" RETURN doc FOR doc IN docs FILTER doc.value == [ 1, 2, 3 ] RETURN doc FOR doc IN docs FILTER doc.value == { foo: "bar" } RETURN doc * INCOMPATIBLE CHANGE: removed undocumented method `collection.saveOrReplace` this feature was never advertised nor documented nor tested. * INCOMPATIBLE CHANGE: removed undocumented REST API method `/_api/simple/BY-EXAMPLE-HASH` this feature was never advertised nor documented nor tested. * added explicit startup parameter `--server.reuse-address` This flag can be used to control whether sockets should be acquired with the SO_REUSEADDR flag. Regardless of this setting, sockets on Windows are always acquired using the SO_EXCLUSIVEADDRUSE flag. * removed undocumented REST API method GET `/_admin/database-name` * added user validation API at POST `/_api/user/` * slightly improved users management API in `/_api/user`: Previously, when creating a new user via HTTP POST, the username needed to be passed in an attribute `username`. When users were returned via this API, the usernames were returned in an attribute named `user`. This was slightly confusing and was changed in 1.5 as follows: - when adding a user via HTTP POST, the username can be specified in an attribute `user`. If this attribute is not used, the API will look into the attribute `username` as before and use that value. - when users are returned via HTTP GET, the usernames are still returned in an attribute `user`. This change should be fully downwards-compatible with the previous version of the API. * added AQL SLICE function to extract slices from lists * removed check-server binary * made module loader more node compatible * the startup option `--javascript.package-path` for arangosh is now deprecated and does nothing. Using it will not cause an error, but the option is ignored. * added coffee script support * Several UI improvements. * Exchanged icons in the graphviewer toolbar * always start networking and HTTP listeners when starting the server (even in console mode) * allow vertex and edge filtering with user-defined functions in TRAVERSAL, TRAVERSAL_TREE and SHORTEST_PATH AQL functions: // using user-defined AQL functions for edge and vertex filtering RETURN TRAVERSAL(friends, friendrelations, "friends/john", "outbound", { followEdges: "myfunctions::checkedge", filterVertices: "myfunctions::checkvertex" }) // using the following custom filter functions -- ArangoDB Maintainer Sat, 08 Feb 2014 22:27:45 +0100 arangodb (1.4.8-1.1) stable; urgency=low * Changed to Version 1.4.8 * install foxx apps in the web interface * fixed a segfault in the import API -- ArangoDB Maintainer Sat, 08 Feb 2014 20:41:13 +0100 arangodb (1.4.9-1.1) stable; urgency=low * Changed to Version 1.4.9 -- ArangoDB Maintainer Fri, 07 Feb 2014 21:49:50 +0100 arangodb (1.4.8-1.1) stable; urgency=low * Changed to Version 1.4.8 -- ArangoDB Maintainer Mon, 27 Jan 2014 13:43:56 +0100 arangodb (1.4.7-1.1) stable; urgency=low * Changed to Version 1.4.7 -- ArangoDB Maintainer Thu, 23 Jan 2014 17:21:31 +0100 arangodb (1.4.6-1.1) stable; urgency=low * Changed to Version 1.4.6 -- ArangoDB Maintainer Mon, 20 Jan 2014 22:15:44 +0100 arangodb (1.4.5-1.1) stable; urgency=low * Changed to Version 1.4.5 -- ArangoDB Maintainer Wed, 15 Jan 2014 17:08:12 +0100 arangodb (1.4.5r2-1.1) stable; urgency=low * Changed to Version 1.4.5-rc2 -- ArangoDB Maintainer Mon, 13 Jan 2014 14:46:37 +0100 arangodb (1.4.5r1-1.1) stable; urgency=low * Changed to Version 1.4.5-rc1 -- ArangoDB Maintainer Fri, 03 Jan 2014 15:30:12 +0100 arangodb (1.4.4-1.1) stable; urgency=low * Changed to Version 1.4.4 -- ArangoDB Maintainer Tue, 24 Dec 2013 10:26:15 +0100 arangodb (1.4.4r1-1.1) stable; urgency=low * Changed to Version 1.4.4-rc1 -- ArangoDB Maintainer Sun, 22 Dec 2013 18:43:40 +0100 arangodb (1.4.3-1.1) stable; urgency=low * Changed to Version 1.4.3 -- ArangoDB Maintainer Mon, 25 Nov 2013 10:41:14 +0100 arangodb (1.4.3a1-1.1) stable; urgency=low * Changed to Version 1.4.3-alpha1 -- ArangoDB Maintainer Fri, 22 Nov 2013 22:11:35 +0100 arangodb (1.4.2-18.4) stable; urgency=low * Changed to Version 1.4.2 -- ArangoDB Maintainer Wed, 20 Nov 2013 14:18:14 +0100 arangodb (1.4.2a1-18.4) stable; urgency=low * Changed to Version 1.4.2-alpha1 -- ArangoDB Maintainer Sat, 09 Nov 2013 19:23:27 +0100 arangodb (1.4.1-18.4) stable; urgency=low * Changed to Version 1.4.1 -- ArangoDB Maintainer Fri, 08 Nov 2013 13:03:44 +0100 arangodb (1.4.1r1-18.4) stable; urgency=low * Changed to Version 1.4.1-rc1 -- ArangoDB Maintainer Thu, 07 Nov 2013 22:57:35 +0100 arangodb (1.4.1r1-18.4) stable; urgency=low * Changed to Version 1.4.1-rc1 -- ArangoDB Maintainer Thu, 07 Nov 2013 21:20:03 +0100 arangodb (1.4.0-18.1) stable; urgency=low * Changed to Version 1.4.0 -- ArangoDB Maintainer Tue, 29 Oct 2013 15:33:15 +0100 arangodb (1.4.0r1-18.1) stable; urgency=low * Changed to Version 1.4.0-rc1 -- Info Tue, 29 Oct 2013 08:55:47 +0100 arangodb (1.4.0b2-18.1) stable; urgency=low * Changed to Version 1.4.0-beta2 -- Info Tue, 22 Oct 2013 16:30:46 +0200 arangodb (1.4.0-16) stable; urgency=low * Changed to Version 1.4.0-alpha1 -- Info Fri, 02 Aug 2013 17:36:00 +0200 arangodb (1.3.2-15) stable; urgency=low * Changed to Version 1.3.2 -- Info Fri, 21 Jun 2013 13:09:00 +0100 arangodb (1.3.1-14) stable; urgency=low * Changed to Version 1.3.1 -- Info Fri, 24 May 2013 18:05:00 +0100 arangodb (1.3.0-13) stable; urgency=low * Changed to Version 1.3.0 -- Info Fri, 10 May 2013 17:12:00 +0100 arangodb (1.2.3-12) stable; urgency=low * Changed to Version 1.2.3 -- Info Fri, 12 Apr 2013 12:35:00 +0100 arangodb (1.2.2-11) stable; urgency=low * Changed to Version 1.2.2 -- Info Tue, 26 Mar 2013 14:48:00 +0100 arangodb (1.2.1-10) stable; urgency=low * Changed to Version 1.2.1 -- Info Fri, 15 Mar 2013 06:28:00 +0100 arangodb (1.2.0-9) stable; urgency=low * Changed to Version 1.2.0 -- Info Fri, 1 Mar 2013 14:15:00 +0100 arangodb (1.2.beta3-9) stable; urgency=low * Changed to Version 1.2.beta3 -- Info Fri, 22 Feb 2013 17:22:00 +0100 arangodb (1.2.beta2-6) stable; urgency=low * Changed to Version 1.2.beta2 -- Info Fri, 15 Feb 2013 14:39:00 +0100 arangodb (1.2.beta1-4) stable; urgency=low * Changed to Version 1.2.beta1 -- Info Mon, 4 Feb 2013 10:02:00 +0100 arangodb (1.1.2-3) stable; urgency=low * Changed to Version 1.1.2 -- Info Mon, 21 Jan 2013 08:29:00 +0100 arangodb (1.1.1-2) stable; urgency=low * Changed to Version 1.1.1 -- Info Tue, 18 Dec 2012 13:50:00 +0100 arangodb (1.1.0-0) stable; urgency=low * Changed to Version 1.1.0 (final) -- Info Wed, 5 Dec 2012 15:05:00 +0100 arangodb (1.1.0-0) stable; urgency=low * Changed to Version 1.1.0 ()beta) -- Info Tue, 16 Oct 2012 07:37:00 +0200 arangodb (1.0.99-0) stable; urgency=low * Initial Release -- Info Wed, 5 Sep 2012 17:50:38 +0200