anchor.diff:  1. <<redis-table-id-generation-strategy, TABLE>>
   2. <<redis-sequence-id-generation-strategy, SEQUENCE>>
   
  -Both strategy will operate in the keys starting with `Identifiers` containing the last value of the id. The difference
  +Both strategies will operate in the keys starting with `Identifiers` containing the last value of the id. The difference
   between the two strategies is the name of the key containing the values.
   
  -Hibernate OGM goes not support the `IDENTITY` strategy and an exception is thrown at startup
  -when it is used.
   The `AUTO` strategy is the same as the <<redis-sequence-id-generation-strategy, SEQUENCE>> one.
   
   The next value is obtained using Redis' http://redis.io/commands/hincrby[HINCRBY] command
  
positive.code: hibernate.ogm.datastore.provider::
  To use Redis as a datastore provider, this property must be set to `redis_experimental`
  hibernate.ogm.datastore.grid_dialect::
  The dialect type how Hibernate OGM Redis maps entities and associations within Redis. The following two dialects exist: `org.hibernate.ogm.datastore.redis.RedisJsonDialect` (store entities as JSON documents within Redis keys. Associations are mapped to Redis lists/sets) and `org.hibernate.ogm.datastore.redis.RedisHashDialect` (store entities as key-value pairs within Redis hashes. Associations are mapped as JSON documents to Redis lists/sets)
  hibernate.ogm.datastore.host::
  The hostname and port of the Redis instance.
  The optional port is concatenated to the host and separated by a colon.
  
negative.code: ----
  Key: News:939c892d-1129-4aff-abf8-e6c26e59dcb
  {
      "title": "On the merits of NoSQL",
      "paper": {
          "name": "NoSQL journal of prophecies",
          "owner": "Delphy"
  