How the aggregate() API call performance differs when used Filter vs Collection of Keys?
(Doc ID 2199679.1)
Last updated on NOVEMBER 19, 2020
Applies to:Oracle Coherence - Version 3.7.1 and later
Information in this document applies to any platform.
When customer used aggregate(), aggregate(Filter filter, InvocableMap.EntryAggregator agent), there is a key which meets the equals(=) filter. But even this, full scan got executed to the data and such behavior will cause high CPU. Customer has fixed the high CPU by ensuring indexes and full scan issue got resolved. But customer doesn't want to use above API because customer is considering that unexpected index issue might occur at any time.
The question is whether full scan would be executed when using aggregate API, aggregate(java.util.Collection collKeys, InvocableMap.EntryAggregator agent). Will there be any potential issues or will it cause any technical problems when using the aggregate() with Collection of keys.
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