anchor.diff:  [[v0.30.0]]
   == 0.30.0 (12.02.2019)
   
  -CAUTION: Java Rest Client: The Gentics Mesh Java REST client which was based on Vert.x was replaced with a OkHttpClient implementation. Some changes to the client interface were necessary to make the client independent of Vert.x. See link:https://getmesh.io/docs/platforms/#_java[this example] and the Javadoc for more information.
  +CAUTION: Java Rest Client: The Gentics Mesh Java REST client which was based on Vert.x was replaced with a `OkHttpClient` implementation. Some changes to the client interface were necessary to make the client independent of Vert.x. See link:https://getmesh.io/docs/platforms/#_java[this example] and the Javadoc for more information.
   
   icon:check[] Clustering: The mesh version will no longer be appended  to the node name used for OrientDB clustering. It is recommended to sanitize the `data/graphdb/storage/distributed-db-config.json` file and remove/rename entries which reference older mesh nodes. Only the active nodes should be listed in the file.
   
  
positive.code: 
  icon:check[] Restore: A `ClassCastException` has been fixed which could be observed directly after a backup restore operation.
  
  icon:check[] Changelog: The automatic backup of orientdb configurations which was executed during the 0.29.0 update has been removed.
  
  [[v0.29.2]]
  == 0.29.2 (18.01.2019)
  
negative.code: 
  icon:plus[] OrientDB 3.0.x: Existing `orientdb-server-config.xml`, `hazelcast.xml`, `default-distributed-db-config.json` configuration files will automatically be moved away and the new configuration files will be created instead.
  
  icon:plus[] OrientDB 3.0.x: A reindex of all vertices and edges will be triggered during the first start-up. This can take some time depending on the database size.
  
  icon:plus[] Memory: The internal overall memory usage has been optimized.
  
  