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: 
  *Fixes*
  
  Various issues with the previous Elasticsearch synchronization mechanism have been adressed.
  
  * Deletion of nodes will now also update documents in the index which reference the deleted node
  * Tag and Tag Family deletion will now correctly update referenced tags, tag families and nodes
  
  *Startup*
  
  Gentics Mesh will no longer wait for Elasticsearch during startup.
  
  *Resiliance*
  
  The resiliance for Elasticsearch server issues has been improved. Failed requests will automatically be retried. If too many issues occure Gentics Mesh will automatically invoke a index sync in order to recover from the issue. This sync will be retried until Elasticsearch becomes responsive again.
  
  *Syncing*
  
  The clear and sync mechanism has been streamlined in order to benefit from other changes like *resiliance*.
  
  ____
  
  NOTE: It is not required to reindex documents since the index names and structure has not been changed.
  
  icon:check[] File Handling: The file upload mechanism has been overhauled to adress issues with blocked uploads which could occure when uploading multiple files in-parallel.
  
  icon:check[] File Handling: Failed Uploads will now remove temporary files from disk. Previously in some error sitations the temporary upload have not been removed.
  
  icon:check[] Permissions: Applying permissions recursively on projects did not affect branches. This has been fixed.
  
  icon:plus[] Permissions: Setting permissions recursively is now done more efficiently.
  
  icon:plus[] Thread Usage: The overall request handling has been refactored to reduce sitations in which the event-loop threads could be blocked. The request handling code has been unified.
  
  
  icon:plus[] Performance: The overall read performance has been improved. The memory usage has been reduced.
  
negative.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)
  