devel

-----

* increase the recommended value for `/proc/sys/vm/max_map_count` to a value

eight times as high as the previous recommended value. Increasing the

values helps to prevent an ArangoDB server from running out of memory mappings.

v3.2.4 (2017-XX-XX)

-------------------

* UI: added replicationFactor option during SmartGraph creation

* make the MMFiles compactor perform less writes during normal compaction

operation

This partially fixes issue #3144

* make the MMFiles compactor configurable

The following options have been added:

* `--compaction.db-sleep-time`: sleep interval between two compaction runs

(in s)

* `--compaction.min-interval"`: minimum sleep time between two compaction

runs (in s)

* `--compaction.min-small-data-file-size`: minimal filesize threshold

original datafiles have to be below for a compaction

* `--compaction.dead-documents-threshold`: minimum unused count of documents

in a datafile

* `--compaction.dead-size-threshold`: how many bytes of the source data file

are allowed to be unused at most

* `--compaction.dead-size-percent-threshold`: how many percent of the source

datafile should be unused at least

* `--compaction.max-files`: Maximum number of files to merge to one file

* `--compaction.max-result-file-size`: how large may the compaction result

file become (in bytes)

* `--compaction.max-file-size-factor`: how large the resulting file may

be in comparison to the collection's `--database.maximal-journal-size' setting`

* fix downwards-incompatibility in /_api/explain REST handler

* fix Windows implementation for fs.getTempPath() to also create a

sub-directory as we do on linux

* fixed a multi-threading issue in cluster-internal communication

* performance improvements for traversals and edge lookups

* removed internal memory zone handling code. the memory zones were a leftover

from the early ArangoDB days and did not provide any value in the current

implementation.

* (Enterprise only) added `skipInaccessibleCollections` option for AQL queries:

if set, AQL queries (especially graph traversals) will treat collections to

which a user has no access rights to as if these collections were empty.

* adjusted scheduler thread handling to start and stop less threads in

normal operations

* leader-follower replication catchup code has been rewritten in C++

* early stage AQL optimization now also uses the C++ implementations of

AQL functions if present. Previously it always referred to the JavaScript

implementations and ignored the C++ implementations. This change gives

more flexibility to the AQL optimizer.

* ArangoDB tty log output is now colored for log messages with levels

FATAL, ERR and WARN.

* changed the return values of AQL functions `REGEX_TEST` and `REGEX_REPLACE`

to `null` when the input regex is invalid. Previous versions of ArangoDB

partly returned `false` for invalid regexes and partly `null`.

* added `--log.role` option for arangod

When set to `true`, this option will make the ArangoDB logger print a single

character with the server's role into each logged message. The roles are:

- U: undefined/unclear (used at startup)

- S: single server

- C: coordinator

- P: primary

- A: agent

The default value for this option is `false`, so no roles will be logged.

v3.2.3 (2017-09-07)

-------------------

* fixed issue #3106: orphan collections could not be registered in general-graph module

* fixed wrong selection of the database inside the internal cluster js api

* added startup option `--server.check-max-memory-mappings` to make arangod check

the number of memory mappings currently used by the process and compare it with

the maximum number of allowed mappings as determined by /proc/sys/vm/max_map_count

The default value is `true`, so the checks will be performed. When the current

number of mappings exceeds 90% of the maximum number of mappings, the creation

of further V8 contexts will be deferred.

Note that this option is effective on Linux systems only.

* arangoimp now has a `--remove-attribute` option

* added V8 context lifetime control options

`--javascript.v8-contexts-max-invocations` and `--javascript.v8-contexts-max-age`

These options allow specifying after how many invocations a used V8 context is

disposed, or after what time a V8 context is disposed automatically after its

creation. If either of the two thresholds is reached, an idl V8 context will be

disposed.

The default value of `--javascript.v8-contexts-max-invocations` is 0, meaning that

the maximum number of invocations per context is unlimited. The default value

for `--javascript.v8-contexts-max-age` is 60 seconds.

* fixed wrong UI cluster health information

* fixed issue #3070: Add index in _jobs collection

* fixed issue #3125: HTTP Foxx API JSON parsing

* fixed issue #3120: Foxx queue: job isn't running when server.authentication = true

* fixed supervision failure detection and handling, which happened with simultaneous

agency leadership change

v3.2.2 (2017-08-23)

-------------------

* make "Rebalance shards" button work in selected database only, and not make

it rebalance the shards of all databases

* fixed issue #2847: adjust the response of the DELETE `/_api/users/database/*` calls

* fixed issue #3075: Error when upgrading arangoDB on linux ubuntu 16.04

* fixed a buffer overrun in linenoise console input library for long input strings

* increase size of the linenoise input buffer to 8 KB

* abort compilation if the detected GCC or CLANG isn't in the range of compilers

we support

* fixed spurious cluster hangups by always sending AQL-query related requests

to the correct servers, even after failover or when a follower drops

The problem with the previous shard-based approach was that responsibilities

for shards may change from one server to another at runtime, after the query

was already instanciated. The coordinator and other parts of the query then

sent further requests for the query to the servers now responsible for the

shards.

However, an AQL query must send all further requests to the same servers on

which the query was originally instanciated, even in case of failover.

Otherwise this would potentially send requests to servers that do not know

about the query, and would also send query shutdown requests to the wrong

servers, leading to abandoned queries piling up and using resources until

they automatically time out.

* fixed issue with RocksDB engine acquiring the collection count values too

early, leading to the collection count values potentially being slightly off

even in exclusive transactions (for which the exclusive access should provide

an always-correct count value)

* fixed some issues in leader-follower catch-up code, specifically for the

RocksDB engine

* make V8 log fatal errors to syslog before it terminates the process.

This change is effective on Linux only.

* fixed issue with MMFiles engine creating superfluous collection journals

on shutdown

* fixed issue #3067: Upgrade from 3.2 to 3.2.1 reset autoincrement keys

* fixed issue #3044: ArangoDB server shutdown unexpectedly

* fixed issue #3039: Incorrect filter interpretation

* fixed issue #3037: Foxx, internal server error when I try to add a new service

* improved MMFiles fulltext index document removal performance

and fulltext index query performance for bigger result sets

* ui: fixed a display bug within the slow and running queries view

* ui: fixed a bug when success event triggers twice in a modal

* ui: fixed the appearance of the documents filter

* ui: graph vertex collections not restricted to 10 anymore

* fixed issue #2835: UI detection of JWT token in case of server restart or upgrade

* upgrade jemalloc version to 5.0.1

This fixes problems with the memory allocator returing "out of memory" when

calling munmap to free memory in order to return it to the OS.

It seems that calling munmap on Linux can increase the number of mappings, at least

when a region is partially unmapped. This can lead to the process exceeding its

maximum number of mappings, and munmap and future calls to mmap returning errors.

jemalloc version 5.0.1 does not have the `--enable-munmap` configure option anymore,

so the problem is avoided. To return memory to the OS eventually, jemalloc 5's

background purge threads are used on Linux.

* fixed issue #2978: log something more obvious when you log a Buffer

* fixed issue #2982: AQL parse error?

* fixed issue #3125: HTTP Foxx API Json parsing

v3.2.1 (2017-08-09)

-------------------

* added C++ implementations for AQL functions `LEFT()`, `RIGHT()` and `TRIM()`

* fixed docs for issue #2968: Collection _key autoincrement value increases on error

* fixed issue #3011: Optimizer rule reduce-extraction-to-projection breaks queries

* Now allowing to restore users in a sharded environment as well

It is still not possible to restore collections that are sharded

differently than by _key.

* fixed an issue with restoring of system collections and user rights.

It was not possible to restore users into an authenticated server.

* fixed issue #2977: Documentation for db._createDatabase is wrong

* ui: added bind parameters to slow query history view

* fixed issue #1751: Slow Query API should provide bind parameters, webui should display them

* ui: fixed a bug when moving multiple documents was not possible

* fixed docs for issue #2968: Collection _key autoincrement value increases on error

* AQL CHAR_LENGTH(null) returns now 0. Since AQL TO_STRING(null) is '' (string of length 0)

* ui: now supports single js file upload for Foxx services in addition to zip files

* fixed a multi-threading issue in the agency when callElection was called

while the Supervision was calling updateSnapshot

* added startup option `--query.tracking-with-bindvars`

This option controls whether the list of currently running queries

and the list of slow queries should contain the bind variables used

in the queries or not.

The option can be changed at runtime using the commands

// enables tracking of bind variables

// set to false to turn tracking of bind variables off

var value = true;

require("@arangodb/aql/queries").properties({

trackBindVars: value

});

* index selectivity estimates are now available in the cluster as well

* fixed issue #2943: loadIndexesIntoMemory not returning the same structure

as the rest of the collection APIs

* fixed issue #2949: ArangoError 1208: illegal name

* fixed issue #2874: Collection properties do not return `isVolatile`

attribute

* potential fix for issue #2939: Segmentation fault when starting

coordinator node

* fixed issue #2810: out of memory error when running UPDATE/REPLACE

on medium-size collection

* fix potential deadlock errors in collector thread

* disallow the usage of volatile collections in the RocksDB engine

by throwing an error when a collection is created with attribute

`isVolatile` set to `true`.

Volatile collections are unsupported by the RocksDB engine, so

creating them should not succeed and silently create a non-volatile

collection

* prevent V8 from issuing SIGILL instructions when it runs out of memory

Now arangod will attempt to log a FATAL error into its logfile in case V8

runs out of memory. In case V8 runs out of memory, it will still terminate the

entire process. But at least there should be something in the ArangoDB logs

indicating what the problem was. Apart from that, the arangod process should

now be exited with SIGABRT rather than SIGILL as it shouldn't return into the

V8 code that aborted the process with `__builtin_trap`.

this potentially fixes issue #2920: DBServer crashing automatically post upgrade to 3.2

* Foxx queues and tasks now ensure that the scripts in them run with the same

permissions as the Foxx code who started the task / queue

* fixed issue #2928: Offset problems

* fixed issue #2876: wrong skiplist index usage in edge collection

* fixed issue #2868: cname missing from logger-follow results in rocksdb

* fixed issue #2889: Traversal query using incorrect collection id

* fixed issue #2884: AQL traversal uniqueness constraints "propagating" to other traversals? Weird results

* arangoexport: added `--query` option for passing an AQL query to export the result

* fixed issue #2879: No result when querying for the last record of a query

* ui: allows now to edit default access level for collections in database

_system for all users except the root user.

* The _users collection is no longer accessible outside the arngod process, _queues is always read-only

* added new option "--rocksdb.max-background-jobs"

* removed options "--rocksdb.max-background-compactions", "--rocksdb.base-background-compactions" and "--rocksdb.max-background-flushes"

* option "--rocksdb.compaction-read-ahead-size" now defaults to 2MB

* change Windows build so that RocksDB doesn't enforce AVX optimizations by default

This fixes startup crashes on servers that do not have AVX CPU extensions

* speed up RocksDB secondary index creation and dropping

* removed RocksDB note in Geo index docs

v3.2.0 (2017-07-20)

-------------------

* fixed UI issues

* fixed multi-threading issues in Pregel

* fixed Foxx resilience

* added command-line option `--javascript.allow-admin-execute`

This option can be used to control whether user-defined JavaScript code

is allowed to be executed on server by sending via HTTP to the API endpoint

`/_admin/execute` with an authenticated user account.

The default value is `false`, which disables the execution of user-defined

code. This is also the recommended setting for production. In test environments,

it may be convenient to turn the option on in order to send arbitrary setup

or teardown commands for execution on the server.

v3.2.beta6 (2017-07-18)

-----------------------

* various bugfixes

v3.2.beta5 (2017-07-16)

-----------------------

* numerous bugfixes

v3.2.beta4 (2017-07-04)

-----------------------

* ui: fixed document view _from and _to linking issue for special characters

* added function `db._parse(query)` for parsing an AQL query and returning information about it

* fixed one medium priority and two low priority security user interface

issues found by owasp zap.

* ui: added index deduplicate options

* ui: fixed renaming of collections for the rocksdb storage engine

* documentation and js fixes for secondaries

* RocksDB storage format was changed, users of the previous beta/alpha versions

must delete the database directory and re-import their data

* enabled permissions on database and collection level

* added and changed some user related REST APIs

* added `PUT /_api/user/{user}/database/{database}/{collection}` to change collection permission

* added `GET /_api/user/{user}/database/{database}/{collection}`

* added optional `full` parameter to the `GET /_api/user/{user}/database/` REST call

* added user functions in the arangoshell `@arangodb/users` module

* added `grantCollection` and `revokeCollection` functions

* added `permission(user, database, collection)` to retrieve collection specific rights

* added "deduplicate" attribute for array indexes, which controls whether inserting

duplicate index values from the same document into a unique array index will lead to

an error or not:

// with deduplicate = true, which is the default value:

db._create("test");

db.test.ensureIndex({ type: "hash", fields: ["tags[*]"], deduplicate: true });

db.test.insert({ tags: ["a", "b"] });

db.test.insert({ tags: ["c", "d", "c"] }); // will work, because deduplicate = true

db.test.insert({ tags: ["a"] }); // will fail

// with deduplicate = false

db._create("test");

db.test.ensureIndex({ type: "hash", fields: ["tags[*]"], deduplicate: false });

db.test.insert({ tags: ["a", "b"] });

db.test.insert({ tags: ["c", "d", "c"] }); // will not work, because deduplicate = false

db.test.insert({ tags: ["a"] }); // will fail

The "deduplicate" attribute is now also accepted by the index creation HTTP

API endpoint POST /_api/index and is returned by GET /_api/index.

* added optimizer rule "remove-filters-covered-by-traversal"

* Debian/Ubuntu installer: make messages about future package upgrades more clear

* fix a hangup in VST

The problem happened when the two first chunks of a VST message arrived

together on a connection that was newly switched to VST.

* fix deletion of outdated WAL files in RocksDB engine

* make use of selectivity estimates in hash, skiplist and persistent indexes

in RocksDB engine

* changed VM overcommit recommendation for user-friendliness

* fix a shutdown bug in the cluster: a destroyed query could still be active

* do not terminate the entire server process if a temp file cannot be created

(Windows only)

* fix log output in the front-end, it stopped in case of too many messages

v3.2.beta3 (2017-06-27)

-----------------------

* numerous bugfixes

v3.2.beta2 (2017-06-20)

-----------------------

* potentially fixed issue #2559: Duplicate _key generated on insertion

* fix invalid results (too many) when a skipping LIMIT was used for a

traversal. `LIMIT x` or `LIMIT 0, x` were not affected, but `LIMIT s, x`

may have returned too many results

* fix races in SSL communication code

* fix invalid locking in JWT authentication cache, which could have

crashed the server

* fix invalid first group results for sorted AQL COLLECT when LIMIT

was used

* fix potential race, which could make arangod hang on startup

* removed `exception` field from transaction error result; users should throw

explicit `Error` instances to return custom exceptions (addresses issue #2561)

* fixed issue #2613: Reduce log level when Foxx manager tries to self heal missing database

* add a read only mode for users and collection level authorization

* removed `exception` field from transaction error result; users should throw

explicit `Error` instances to return custom exceptions (addresses issue #2561)

* fixed issue #2677: Foxx disabling development mode creates non-deterministic service bundle

* fixed issue #2684: Legacy service UI not working

v3.2.beta1 (2017-06-12)

-----------------------

* provide more context for index errors (addresses issue #342)

* arangod now validates several OS/environment settings on startup and warns if

the settings are non-ideal. Most of the checks are executed on Linux systems only.

* fixed issue #2515: The replace-or-with-in optimization rule might prevent use of indexes

* added `REGEX_REPLACE` AQL function

* the RocksDB storage format was changed, users of the previous alpha versions

must delete the database directory and re-import their data

* added server startup option `--query.fail-on-warning`

setting this option to `true` will abort any AQL query with an exception if

it causes a warning at runtime. The value can be overridden per query by

setting the `failOnWarning` attribute in a query's options.

* added --rocksdb.num-uncompressed-levels to adjust number of non-compressed levels

* added checks for memory managment and warn (i. e. if hugepages are enabled)

* set default SSL cipher suite string to "HIGH:!EXPORT:!aNULL@STRENGTH"

* fixed issue #2469: Authentication = true does not protect foxx-routes

* fixed issue #2459: compile success but can not run with rocksdb

* `--server.maximal-queue-size` is now an absolute maximum. If the queue is

full, then 503 is returned. Setting it to 0 means "no limit".

* (Enterprise only) added authentication against an LDAP server

* fixed issue #2083: Foxx services aren't distributed to all coordinators

* fixed issue #2384: new coordinators don't pick up existing Foxx services

* fixed issue #2408: Foxx service validation causes unintended side-effects

* extended HTTP API with routes for managing Foxx services

* added distinction between hasUser and authorized within Foxx

(cluster internal requests are authorized requests but don't have a user)

* arangoimp now has a `--threads` option to enable parallel imports of data

* PR #2514: Foxx services that can't be fixed by self-healing now serve a 503 error

* added `time` function to `@arangodb` module

v3.2.alpha4 (2017-04-25)

------------------------

* fixed issue #2450: Bad optimization plan on simple query

* fixed issue #2448: ArangoDB Web UI takes no action when Delete button is clicked

* fixed issue #2442: Frontend shows already deleted databases during login

* added 'x-content-type-options: nosniff' to avoid MSIE bug

* set default value for `--ssl.protocol` from TLSv1 to TLSv1.2.

* AQL breaking change in cluster:

The SHORTEST_PATH statement using edge-collection names instead

of a graph name now requires to explicitly name the vertex-collection names

within the AQL query in the cluster. It can be done by adding `WITH <name>`

at the beginning of the query.

Example:

```

FOR v,e IN OUTBOUND SHORTEST_PATH @start TO @target edges [...]

```

Now has to be:

```

WITH vertices

FOR v,e IN OUTBOUND SHORTEST_PATH @start TO @target edges [...]

```

This change is due to avoid dead-lock sitations in clustered case.

An error stating the above is included.

* add implicit use of geo indexes when using SORT/FILTER in AQL, without

the need to use the special-purpose geo AQL functions `NEAR` or `WITHIN`.

the special purpose `NEAR` AQL function can now be substituted with the

following AQL (provided there is a geo index present on the `doc.latitude`

and `doc.longitude` attributes):

FOR doc in geoSort

SORT DISTANCE(doc.latitude, doc.longitude, 0, 0)

LIMIT 5

RETURN doc

`WITHIN` can be substituted with the following AQL:

FOR doc in geoFilter

FILTER DISTANCE(doc.latitude, doc.longitude, 0, 0) < 2000

RETURN doc

Compared to using the special purpose AQL functions this approach has the

advantage that it is more composable, and will also honor any `LIMIT` values

used in the AQL query.

* potential fix for shutdown hangs on OSX

* added KB, MB, GB prefix for integer parameters, % for integer parameters

with a base value

* added JEMALLOC 4.5.0

* added `--vm.resident-limit` and `--vm.path` for file-backed memory mapping

after reaching a configurable maximum RAM size

* try recommended limit for file descriptors in case of unlimited

hard limit

* issue #2413: improve logging in case of lock timeout and deadlocks

* added log topic attribute to /_admin/log api

* removed internal build option `USE_DEV_TIMERS`

Enabling this option activated some proprietary timers for only selected

events in arangod. Instead better use `perf` to gather timings.

v3.2.alpha3 (2017-03-22)

------------------------

* increase default collection lock timeout from 30 to 900 seconds

* added function `db._engine()` for retrieval of storage engine information at

server runtime

There is also an HTTP REST handler at GET /_api/engine that returns engine

information.

* require at least cmake 3.2 for building ArangoDB

* make arangod start with less V8 JavaScript contexts

This speeds up the server start (a little bit) and makes it use less memory.

Whenever a V8 context is needed by a Foxx action or some other operation and

there is no usable V8 context, a new one will be created dynamically now.

Up to `--javascript.v8-contexts` V8 contexts will be created, so this option

will change its meaning. Previously as many V8 contexts as specified by this

option were created at server start, and the number of V8 contexts did not

change at runtime. Now up to this number of V8 contexts will be in use at the

same time, but the actual number of V8 contexts is dynamic.

The garbage collector thread will automatically delete unused V8 contexts after

a while. The number of spare contexts will go down to as few as configured in

the new option `--javascript.v8-contexts-minimum`. Actually that many V8 contexts

are also created at server start.

The first few requests in new V8 contexts will take longer than in contexts

that have been there already. Performance may therefore suffer a bit for the

initial requests sent to ArangoDB or when there are only few but performance-

critical situations in which new V8 contexts will be created. If this is a

concern, it can easily be fixed by setting `--javascipt.v8-contexts-minimum`

and `--javascript.v8-contexts` to a relatively high value, which will guarantee

that many number of V8 contexts to be created at startup and kept around even

when unused.

Waiting for an unused V8 context will now also abort if no V8 context can be

acquired/created after 120 seconds.

* improved diagnostic messages written to logfiles by supervisor process

* fixed issue #2367

* added "bindVars" to attributes of currently running and slow queries

* added "jsonl" as input file type for arangoimp

* upgraded version of bundled zlib library from 1.2.8 to 1.2.11

* added input file type `auto` for arangoimp so it can automatically detect the

type of the input file from the filename extension

* fixed variables parsing in GraphQL

* added `--translate` option for arangoimp to translate attribute names from

the input files to attriubte names expected by ArangoDB

The `--translate` option can be specified multiple times (once per translation

to be executed). The following example renames the "id" column from the input

file to "_key", and the "from" column to "_from", and the "to" column to "_to":

arangoimp --type csv --file data.csv --translate "id=_key" --translate "from=_from" --translate "to=_to"

`--translate` works for CSV and TSV inputs only.

* changed default value for `--server.max-packet-size` from 128 MB to 256 MB

* fixed issue #2350

* fixed issue #2349

* fixed issue #2346

* fixed issue #2342

* change default string truncation length from 80 characters to 256 characters for

`print`/`printShell` functions in ArangoShell and arangod. This will emit longer

prefixes of string values before truncating them with `...`, which is helpful

for debugging.

* always validate incoming JSON HTTP requests for duplicate attribute names

Incoming JSON data with duplicate attribute names will now be rejected as

invalid. Previous versions of ArangoDB only validated the uniqueness of

attribute names inside incoming JSON for some API endpoints, but not

consistently for all APIs.

* don't let read-only transactions block the WAL collector

* allow passing own `graphql-sync` module instance to Foxx GraphQL router

* arangoexport can now export to csv format

* arangoimp: fixed issue #2214

* Foxx: automatically add CORS response headers

* added "OPTIONS" to CORS `access-control-allow-methods` header

* Foxx: Fix arangoUser sometimes not being set correctly

* fixed issue #1974

v3.2.alpha2 (2017-02-20)

------------------------

* ui: fixed issue #2065

* ui: fixed a dashboard related memory issue

* Internal javascript rest actions will now hide their stack traces to the client

unless maintainer mode is activated. Instead they will always log to the logfile

* Removed undocumented internal HTTP API:

* PUT _api/edges

The documented GET _api/edges and the undocumented POST _api/edges remains unmodified.

* updated V8 version to 5.7.0.0

* change undocumented behaviour in case of invalid revision ids in

If-Match and If-None-Match headers from 400 (BAD) to 412 (PRECONDITION

FAILED).

* change undocumented behaviour in case of invalid revision ids in

JavaScript document operations from 1239 ("illegal document revision")

to 1200 ("conflict").

* added data export tool, arangoexport.

arangoexport can be used to export collections to json, jsonl or xml

and export a graph or collections to xgmml.

* fixed a race condition when closing a connection

* raised default hard limit on threads for very small to 64

* fixed negative counting of http connection in UI

v3.2.alpha1 (2017-02-05)

------------------------

* added figure `httpRequests` to AQL query statistics

* removed revisions cache intermediate layer implementation

* obsoleted startup options `--database.revision-cache-chunk-size` and

`--database.revision-cache-target-size`

* fix potential port number over-/underruns

* added startup option `--log.shorten-filenames` for controlling whether filenames

in log messages should be shortened to just the filename with the absolute path

* removed IndexThreadFeature, made `--database.index-threads` option obsolete

* changed index filling to make it more parallel, dispatch tasks to boost::asio

* more detailed stacktraces in Foxx apps

* generated Foxx services now use swagger tags

v3.1.24 (XXXX-XX-XX)

--------------------

* fixed one more LIMIT issue in traversals

v3.1.23 (2017-06-19)

--------------------

* potentially fixed issue #2559: Duplicate _key generated on insertion

* fix races in SSL communication code

* fix invalid results (too many) when a skipping LIMIT was used for a

traversal. `LIMIT x` or `LIMIT 0, x` were not affected, but `LIMIT s, x`

may have returned too many results

* fix invalid first group results for sorted AQL COLLECT when LIMIT

was used

* fix invalid locking in JWT authentication cache, which could have

crashed the server

* fix undefined behavior in traverser when traversals were used inside

a FOR loop

v3.1.22 (2017-06-07)

--------------------

* fixed issue #2505: Problem with export + report of a bug

* documented changed behavior of WITH

* fixed ui glitch in aardvark

* avoid agency compaction bug

* fixed issue #2283: disabled proxy communication internally

v3.1.21 (2017-05-22)

--------------------

* fixed issue #2488: AQL operator IN error when data use base64 chars

* more randomness in seeding RNG

v3.1.20 (2016-05-16)

--------------------

* fixed incorrect sorting for distributeShardsLike

* improve reliability of AgencyComm communication with Agency

* fixed shard numbering bug, where ids were erouneously incremented by 1

* remove an unnecessary precondition in createCollectionCoordinator

* funny fail rotation fix

* fix in SimpleHttpClient for correct advancement of readBufferOffset

* forward SIG_HUP in supervisor process to the server process to fix logrotaion

You need to stop the remaining arangod server process manually for the upgrade to work.

v3.1.19 (2017-04-28)

--------------------

* Fixed a StackOverflow issue in Traversal and ShortestPath. Occured if many (>1000) input

values in a row do not return any result. Fixes issue: #2445

* fixed issue #2448

* fixed issue #2442

* added 'x-content-type-options: nosniff' to avoid MSIE bug

* fixed issue #2441

* fixed issue #2440

* Fixed a StackOverflow issue in Traversal and ShortestPath. Occured if many (>1000) input

values in a row do not return any result. Fixes issue: #2445

* fix occasional hanging shutdowns on OS X

v3.1.18 (2017-04-18)

--------------------

* fixed error in continuous synchronization of collections

* fixed spurious hangs on server shutdown

* better error messages during restore collection

* completely overhaul supervision. More detailed tests

* Fixed a dead-lock situation in cluster traversers, it could happen in

rare cases if the computation on one DBServer could be completed much earlier

than the other server. It could also be restricted to SmartGraphs only.

* (Enterprise only) Fixed a bug in SmartGraph DepthFirstSearch. In some

more complicated queries, the maxDepth limit of 1 was not considered strictly

enough, causing the traverser to do unlimited depth searches.

* fixed issue #2415

* fixed issue #2422

* fixed issue #1974

v3.1.17 (2017-04-04)

--------------------

* (Enterprise only) fixed a bug where replicationFactor was not correctly

forwarded in SmartGraph creation.

* fixed issue #2404

* fixed issue #2397

* ui - fixed smart graph option not appearing

* fixed issue #2389

* fixed issue #2400

v3.1.16 (2017-03-27)

--------------------

* fixed issue #2392

* try to raise file descriptors to at least 8192, warn otherwise

* ui - aql editor improvements + updated ace editor version (memory leak)

* fixed lost HTTP requests

* ui - fixed some event issues

* avoid name resolution when given connection string is a valid ip address

* helps with issue #1842, bug in COLLECT statement in connection with LIMIT.

* fix locking bug in cluster traversals

* increase lock timeout defaults

* increase various cluster timeouts

* limit default target size for revision cache to 1GB, which is better for

tight RAM situations (used to be 40% of (totalRAM - 1GB), use

--database.revision-cache-target-size <VALUEINBYTES> to get back the

old behaviour

* fixed a bug with restarted servers indicating status as "STARTUP"

rather that "SERVING" in Nodes UI.

v3.1.15 (2017-03-20)

--------------------

* add logrotate configuration as requested in #2355

* fixed issue #2376

* ui - changed document api due a chrome bug

* ui - fixed a submenu bug

* added endpoint /_api/cluster/endpoints in cluster case to get all

coordinator endpoints

* fix documentation of /_api/endpoint, declaring this API obsolete.

* Foxx response objects now have a `type` method for manipulating the content-type header

* Foxx tests now support `xunit` and `tap` reporters

v3.1.14 (2017-03-13)

--------------------

* ui - added feature request (multiple start nodes within graph viewer) #2317

* added missing locks to authentication cache methods

* ui - added feature request (multiple start nodes within graph viewer) #2317

* ui - fixed wrong merge of statistics information from different coordinators

* ui - fixed issue #2316

* ui - fixed wrong protocol usage within encrypted environment

* fixed compile error on Mac Yosemite

* minor UI fixes

v3.1.13 (2017-03-06)

--------------------

* fixed variables parsing in GraphQL

* fixed issue #2214

* fixed issue #2342

* changed thread handling to queue only user requests on coordinator