anchor.diff:  
   For more information, please refer to the
   http://api.mongodb.org/java/current/com/mongodb/WriteConcern.html[official documentation].
  -This option is case insensitive and the default value is +ACKNOWLEDGED+.
   
   [NOTE]
   ====
  
positive.code: Possible settings are (values of the +WriteConcernType+ enum):
  +ERRORS_IGNORED+, +ACKNOWLEDGED+, +UNACKNOWLEDGED+, +FSYNCED+, +JOURNALED+, +REPLICA_ACKNOWLEDGED+, +MAJORITY+ and +CUSTOM+.
  When set to +CUSTOM+, a custom +WriteConcern+ implementation type has to be specified.
  hibernate.ogm.mongodb.write_concern_type::
  Specifies a custom +WriteConcern+ implementation type (fully-qualified name, class object or instance).
  This is useful in cases where the pre-defined configurations are not sufficient,
  
negative.code: hibernate.ogm.datastore.document.association_storage::
  Defines the way OGM stores association information in MongoDB.
  The following two strategies exist (values of the +org.hibernate.ogm.datastore.document.options.AssociationStorageType+ enum):
  
  * +IN_ENTITY+: store association information within the entity
  * +ASSOCIATION_DOCUMENT+: store association information in a dedicated document per association
  
  +
  +IN_ENTITY+ is the default and recommended option
  unless the association navigation data is much bigger than the core of the document and leads to performance degradation.
  hibernate.ogm.mongodb.association_document_storage::
  Defines how to store assocation documents (applies only if the +ASSOCIATION_DOCUMENT+
  association storage strategy is used).
  Possible strategies are (values of the +org.hibernate.ogm.datastore.mongodb.options.AssociationDocumentType+ enum):
  
  * +GLOBAL_COLLECTION+ (default): stores the association information in a unique MongoDB collection for all associations
  * +COLLECTION_PER_ASSOCIATION+ stores the association in a dedicated MongoDB collection per association
  hibernate.ogm.mongodb.write_concern::
  