[ https://issues.apache.org/jira/browse/IGNITE-16004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737363#comment-17737363 ]
Igor Sapego commented on IGNITE-16004: -------------------------------------- Guys, I have tests in C++ client that show that order still is not preserved. For example: {{code:cpp}} std::vector<test_key_type> non_existing = {test_key_type(1), test_key_type(2)}; auto res = kv_view.remove_all(nullptr, non_existing); EXPECT_EQ(res.size(), 2); // TODO: Key order should be preserved by the server (IGNITE-16004). EXPECT_EQ(2, res[0].key); EXPECT_EQ(1, res[1].key); {{code}} > Preserve key order in InternalTableImpl#collectMultiRowsResponses > ----------------------------------------------------------------- > > Key: IGNITE-16004 > URL: https://issues.apache.org/jira/browse/IGNITE-16004 > Project: Ignite > Issue Type: Bug > Reporter: Alexey Scherbakov > Assignee: Kirill Tkalenko > Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-beta2 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)