[
https://issues.apache.org/jira/browse/IGNITE-20435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Sapego updated IGNITE-20435:
---------------------------------
Description:
The IGNITE-16004 fixed ordering for the most multi key methods but not for the
removeAll methods.
For example, removeAll(1, 2, 3) should return 1, 3 if values for 1 and 3 do not
exist, but in practice this order may be broken
*UPD*
The same issue appears for deleteAllExact and insertAll. These two issues
should be fixed here.
was:
The IGNITE-16004 fixed ordering for the most multi key methods but not for the
removeAll methods.
For example, removeAll(1, 2, 3) should return 1, 3 if a value for 1 and 3
doesn't exists, but in practice this order may be broken
*UPD*
The same issue appears for deleteAllExact and insertAll. These two issues
should be fixed here.
> Preserve key order in batch opperations (deleteAll, deleteAllExact, insertAll)
> ------------------------------------------------------------------------------
>
> Key: IGNITE-20435
> URL: https://issues.apache.org/jira/browse/IGNITE-20435
> Project: Ignite
> Issue Type: Bug
> Reporter: Igor Sapego
> Assignee: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0
>
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> The IGNITE-16004 fixed ordering for the most multi key methods but not for
> the removeAll methods.
> For example, removeAll(1, 2, 3) should return 1, 3 if values for 1 and 3 do
> not exist, but in practice this order may be broken
> *UPD*
> The same issue appears for deleteAllExact and insertAll. These two issues
> should be fixed here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
