anchor.diff:  This doesn't affect how entities are encoded so the specified schema is expected to be compatible with the generated one.
   This can be used to defined server side indexes on caches used by JPQL and native Ickle queries.
   
  +hibernate.ogm.cache.transaction.mode::
  +Property is used to configure the transaction mode of Infinispan caches.
  +Possible values are: `XA`, `NON_DURABLE_XA` (the default), `NON_XA` and `NONE` (the one to disable transaction).
  +For more information see the chapter <<infinispan-remote-transaction>>.
  +
   ==== Data encoding: Protobuf Schema
   
   Using the _Infinispan Remote_ backend your data will be encoded using Protocol Buffers,
  
positive.code: ----
  <infinispan><cache-container>
    <distributed-cache-configuration name="configuration">
       <locking striping="false" acquire-timeout="10000" concurrency-level="50" isolation="READ_COMMITTED"/>
       <transaction mode="NON_DURABLE_XA" />
       <expiration max-idle="-1" />
       <indexing index="NONE" />
       <state-transfer timeout="480000" await-initial-transfer="true" />
    </distributed-cache-configuration>
  </cache-container></infinispan>"
  ====
  
  To apply a custom configuration to a newly created cache
  
negative.code: ==== Remote Query Capability
  
  Hibernate OGM backend is able to run the queries it needs to materialize relations.
  Since version __5.4.0.Alpha2__, the dialect is capable to translate JPQL to the **corresponding** Infinispan remote queries
  or to execute native queries.
  But there are still some limitations:
  
  