anchor.diff:  * Selecting from associations is not yet implemented (example: select h.author.name from Hypothesis h where author is a one-to-one association)
   * Query on Byte filed is currently unsupported
   
  +[[infinispan-remote-transaction]]
  +
  +==== Infinispan Remote Transaction
  +
  +Since version __5.4.0.CR1__, transactions over HotRot client are finally available.
  +In order to fallback to the previous behavior will be necessary just to set property 'hibernate.ogm.cache.transaction.mode' property to `NONE` value.
  +With mode set to NONE transactions are disabled, then the client will be able to handle both transactional and no transactional caches.
  +In contrast, if transactions are enabled, by default they are, __all cache should be defined transactional__.
  +In other word, at the moment, a transactional client cannot handle non transactional caches.
  +For this reason, the default configuration for client side defined caches uses the same transaction mode of the client.
  +
  +Transaction are implemented by Infinispan HotRod client mimicking the embedded `Repeatable Read`
  +and the `Optimistic Locking` semantics.
  +Even if it is mandatory, with current Infinispan version, define them with:
  +
  +1. Pessimistic locking
  +2. REPEATABLE_READ as isolation level
  +
  +In fact, these ones are now also the current values of the default configuration for client side defined caches.
  +
  +Is important to stress the fact that even if the caches must be defined with a pessimistic lock,
  +the behavior seen by the client it is the same that we would have with an optimistic lock.
  +
  +For more information about HotRod transaction see the http://infinispan.org/docs/dev/user_guide/user_guide.html#hot_rod_transaction[Infinispan user guide].
  +
   ==== Known Limitations & Future improvements
   
   The Infinispan Remote dataprovider has some known limitations, some of which are
   unsolvable without further development of Infinispan itself.
  -
  -Transaction Support::
  -We're eagerly waiting for Infinispan to support transactions over Hot Rod, as it
  -already provides this feature in Embedded Mode.
   
   Indexing::
   Infinispan supports Hibernate Search annotations directly embedded within its protobuf
  
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: 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,
  