anchor.diff:  
   If you would like the OGM to manage your schema creation there are several ways to go about it.
   
  -Only classes marked with `@Index` will be used. Indexes will always be generated with the containing class's label and the annotated property's name.
  +Only classes marked with `@Index`, `@CompositeIndex` or `@Required` will be used.
  +Indexes will always be generated with the containing class's label and the annotated property's name.
  +An abstract class containing indexes or constraints must have `@NodeEntity` annotation present.
   Index generation behaviour can be defined in `ogm.properties` by defining a property called: `indexes.auto` and providing a value of:
   
   Below is a table of all options available for configuring Auto-Indexing.
  
positive.code: The primary key is solely provided by the `@Id` annotation.
  See <<reference:annotating-entities:entity-identifier, Entity identifier>> for more information.
  
  [[reference:indexing:creation]]
  == Index Creation
  
  
negative.code: | indexes.auto=assert
  | config.setAutoIndex("assert");
  
  | *update*
  | Builds indexes based on whatever is represented in OGM by `@Index`. Indexes will be changed to constraints and vise versa if the definition in db differs from metadata.
   Handy during development
  | indexes.auto=update
  | config.setAutoIndex("update");
  
  | *dump*
  | Dumps the generated constraints and indexes to a file. Good for setting up environments. none: Default. Simply marks the field as using an index.
  | indexes.auto=dump
  