anchor.diff:  * +-v+ if an index is in the +FAILED+ state, print a verbose error cause if available
   
   Indexes and constraints can be created or removed using Cypher or the Java Core API. They are updated automatically
  -whenever the graph is changed.  See <<graphdb-neo4j-schema>> for more.
  +whenever the graph is changed.  See <<graphdb-neo4j-schema>> for more information.
   
   [[shell-legacy-indexing]]
   === Legacy Indexing ===
  
positive.code: === Setting, renaming and removing properties ===
  Property operations are done with the +set+, +mv+ and +rm+ commands.
  These commands operates on the current node/relationship.
  * +set <key> <value>+ with optionally the +-t+ option (for value type) sets a property.
  Supports every type of value that Neo4j supports. Examples of a property of type +int+:
  [source,plain]
  ----
  $ set -t int age 29
  ----
  
  And an example of setting a +double[]+ property:
  [source,plain]
  ----
  $ set -t double[] my_values [1.4,12.2,13]
  ----
  
  Example of setting a +String+ property containing a JSON string:
  [source,plain]
  ----
  mkrel -c -d i -t DOMAIN_OF --np "{'app':'foobar'}"
  
negative.code: [NOTE]
  This command does not list legacy indexes. For working with legacy indexes, please see <<shell-legacy-indexing>>.
  
  
  List all indexes and constraints:
  
  [source]
  ----
  schema
  ----
  
  List indexes or constraints on +:Person+ nodes for the property +name+:
  
  [source]
  ----
  schema -l :Person -p name
  ----
  
  The +schema+ command supports the following parameters:
  
  