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