Could you please help me. I'm really interesting in the EscapeAll option.
Thanks in advance,
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If
you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
In Ignite H2 indexing became the default mechanism, thus there is no H2 IndexingSPI anymore. Even though there is a way to set an indexing SPI, it is intended for other query implementations.
Former H2 indexing SPI properties were moved to cache configuration and CacheTypeMetadata. As for the setDefaultIndexPrimitiveKey property, you simply need to include your key-value type pair into CacheConfiguration.setIndexedTypes like this:
First thank you for the clarification. Secondly, when do you need to index the key. For example if I do a cache.get(myKey) do you use the indexing part for that?
In my case keys are just opaque identifiers where only their hash and equals are important / relevant.
First thank you for the clarification. Secondly, when do you need to index
Please read carefully javadoc for CacheConfiguration.setIndexedTypes
method. It is not just an array of indexed types, it is a array of
key-value type pairs. This pair is needed to construct SQL table correctly
(Ignite allows you to expose SQL fields for key as well as for value).
For example if I do a cache.get(myKey) do you use the indexing part
Operation cache.get(key) has nothing to do with indexes.
In my case key are just opaque identifier where only its has and its equals
are important / relevant.
Since indexes are sorted data structures and key is always indexed it is preferable to implement Comparable for key as well.