From 89e3480e1f7f1e7cbb99b75ffd1f2d847f9dc606 Mon Sep 17 00:00:00 2001
From: Michael Hackstein <michael@arangodb.com>
Date: Thu, 20 Apr 2017 15:58:02 +0200
Subject: [PATCH] Updated CHANGELOG. Clustered ShortestPath queries now require
 to explicitly name all Vertex Collections that can be encountered during the
 search in the AQL statement in order to avoid cluster deadlocks.

---
 CHANGELOG | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/CHANGELOG b/CHANGELOG
index d385b43ec4..99e3aaf8dd 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,6 +1,27 @@
 devel
 -----
 
+* AQL Breaking Chance 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.
+
 * issue #2413: improve logging in case of lock timeout and deadlocks
 
 * added log topic attribute to /_admin/log api