Does Read-Only Extend Clients Require KeyAssociator Implementation?
(Doc ID 2624962.1)
Last updated on JANUARY 25, 2021
Applies to:Oracle Coherence - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
The customer architecture is using the clients as read only clients (CQC), the data in the caches is inserted/updated by a disabled storage cluster-member process and the clients are just CQC clients. As per the <Note 1434293.1> and the explanation in the documentation page leads to believe that when the clients are just performing read operations the KeyAssociator implementation in the client should not be needed. Could you confirm if this understanding is right or else should the KeyAssociator implementation be added as well for read-only remote clients?
Just to clarify it, the customer is inserting data into the cache using a storage-disabled member of the Coherence cluster (i.e. not a coherence client) and then the clients (CQC clients) just query the data from the cache. In this scenario and given the key associator is defined in the cache config the expectation is user needs to set defer-key-association to true. If the customer wants to set the defer-key-association to false then user should have the key associator defined in the client, remove the key associator definition in the cache config in the server side.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document