[ 
https://issues.apache.org/jira/browse/IGNITE-10576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Seliverstov updated IGNITE-10576:
--------------------------------------
    Description: 
The current UpdateSourceIterator implementation doesn't suit Cache API needs. 
It should be able to mix operation types per key. 

For example we may execute putAll operation with a half of keys are having 
values and a half aren't, this way we should mix DELETE operation for 
null-value keys and PUT operation for others.

Another use case is a transform operation which should turn into a number of 
PUT/UPDATE/DELETE operations on a backup node.

  was:
Current the UpdateSourceIterator implementation doesn't suit Cache API needs. 
It should be able to mix operation types per key. 

For example we may execute putAll operation with a half of keys are having 
values and a half aren't, this way we should mix DELETE operation for 
null-value keys and PUT operation for others.

Another use case is a transform operation which should turn into a number of 
PUT/UPDATE/DELETE operations on a backup node.


> MVCC TX: Rework UpdateSourceIterator to mix operation types
> -----------------------------------------------------------
>
>                 Key: IGNITE-10576
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10576
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Igor Seliverstov
>            Assignee: Andrew Mashenkov
>            Priority: Major
>
> The current UpdateSourceIterator implementation doesn't suit Cache API needs. 
> It should be able to mix operation types per key. 
> For example we may execute putAll operation with a half of keys are having 
> values and a half aren't, this way we should mix DELETE operation for 
> null-value keys and PUT operation for others.
> Another use case is a transform operation which should turn into a number of 
> PUT/UPDATE/DELETE operations on a backup node.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to