[
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 a value for 1 and 3
doesn't exists, but in practice this order may be broken.
was:
After the IGNITE-15085 multi key methods return a List of values correponding
to the passed keys order, where each position correponds to the result
operation for a key with the same position in the arguments.
For example, getAll(1, 2, 3) will return A, null, C if a value for 2 doesn't
exists.
collectMultiRowsResponses can break this ordering for multi partition requests.
> Preserve key order in InternalTableImpl#deleteAll
> -------------------------------------------------
>
> Key: IGNITE-20435
> URL: https://issues.apache.org/jira/browse/IGNITE-20435
> Project: Ignite
> Issue Type: Bug
> Reporter: Igor Sapego
> Priority: Major
> Labels: ignite-3
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
