]
Manik Surtani updated ISPN-1988:
--------------------------------
Summary: Coalesce updates to a given key to a single operation within a transaction
(was: coalesce same key writes within a transaction)
Coalesce updates to a given key to a single operation within a
transaction
--------------------------------------------------------------------------
Key: ISPN-1988
URL:
https://issues.jboss.org/browse/ISPN-1988
Project: Infinispan
Issue Type: Feature Request
Components: Transactions
Affects Versions: 5.1.4.FINAL
Reporter: Mircea Markus
Assignee: Mircea Markus
Labels: optimisation, transaction
Fix For: 5.2.0.FINAL
Following code run with optimistic caches:
start tx
put k, v1
put k, v2
put k, v3
commit
Would cause the PrepareCommand that is sent around to contain 3 PutKeyvalueCommands which
is sub-optimal. What we can do is to only send the last written value (i.e. k v3) and
ignore the previous two (reuse the code in AsyncCacheStore). Besides reducing the payload,
from this would benefit the AtomicHashMaps which uses this code quite a lot and also the
OptimisticLockingInterceptor which would not attempt to order the keys.
I guess this should be a feature that is disabled by default, as I don't think it is
required in general. Might as well be not configurable, enabled by default feature.
Comments?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: