Details
-
Bug
-
Resolution: Obsolete
-
Major
-
None
-
9.1.0.Alpha1
-
None
Description
When a functional command executes a modification on non-owner within transaction, and later in the same transaction we iterate through entry set (e.g. through cache.size()), the functional modification is ignored.
Regular commands store the modified value in context, but functional commands don't have the previous value on originator. Therefore, streams have to retrieve such modified entries into context and re-execute the modifications upon these.
Attachments
Issue Links
- relates to
-
ISPN-7505 Non-functional read in transaction with modifications returns old value
- Closed