[ https://issues.apache.org/jira/browse/IGNITE-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-9689: ------------------------------------ Labels: mvcc_performance (was: ) > MVCC: Optimize filter usage in MvccUpdateDataRow. > ------------------------------------------------- > > Key: IGNITE-9689 > URL: https://issues.apache.org/jira/browse/IGNITE-9689 > Project: Ignite > Issue Type: Task > Components: cache, mvcc > Reporter: Andrew Mashenkov > Priority: Major > Labels: mvcc_performance > Fix For: 2.8 > > > PutIfAbsent and all Replace operation uses filter for previous values checks. > When filter has provided then we have to retrieve full row (instead of > header) just to apply the filter. > However, in most of cases filter doesn't need a value itself, but just a fact > if previous value exists. > There is unused class > org.apache.ignite.internal.processors.cache.CacheOperationFilter enum that > can be used for optimization. We can just compare filter type and visitor > resultType to make a decision in CacheDataStore.mvccUpdate\mvccRemove methods. -- This message was sent by Atlassian JIRA (v7.6.3#76005)