anchor.diff:  Additionally, when removing a {prodname} Oracle connector that uses the Infinispan buffer, the persisted cache files are not removed from disk automatically.
   If the same buffer location will be used by a new connector deployment, the files should be removed manually before deploying the new connector.
   ====
  +
  +===== Infinispan Hotrod client integration
  +
  +The {prodname} Oracle connector utilizes the Hotrod client to communicate with the Infinispan cluster.
  +Any connector property that is prefixed with `log.mining.buffer.infinispan.client.` will be passed directly to the Hotrod client using the `infinispan.client.` namespace, allowing for complete customization of how the client is to interact with the cluster.
  +
  +There is at least one required configuration property that must be supplied when using this Infinspan mode:
  +
  +`log.mining.buffer.infinispan.client.hotrod.server_list`::
  +Specifies the list of Infinispan server hostname and port combinations, using `<hostname>:<port>` format.
   endif::community[]
   
   // Type: concept
  
positive.code: The infinispan option requires that you specify a cache file directory.
  Use the `log.mining.buffer.location` property to define the location for storing cache files.
  
  |[[oracle-property-log-mining-buffer-location]]<<oracle-property-log-mining-buffer-location, `+log.mining.buffer.location+`>>
  |No default
  |Specifies the location of the directory that the connector uses to read and write the buffer cache.
  Specify a directory that every node in the Kafka cluster can access and that is unique for the connector deployment.
  endif::community[]
  
  |[[oracle-property-log-mining-buffer-drop-on-stop]]<<oracle-property-log-mining-buffer-drop-on-stop, `+log.mining.buffer.drop.on.stop+`>>
  |`false`
  
negative.code: The default behavior is that the buffer state is always retained between restarts. +
   +
  Set to `true` only in testing or development environments.
  endif::community[]
  
  |[[oracle-property-log-mining-batch-size-min]]<<oracle-property-log-mining-batch-size-min, `+log.mining.batch.size.min+`>>
  |`1000`
  