You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2022/12/01 14:47:00 UTC
[jira] [Updated] (IGNITE-18243) Implement a peek method for the sorted index cursor
[ https://issues.apache.org/jira/browse/IGNITE-18243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kirill Tkalenko updated IGNITE-18243:
-------------------------------------
Fix Version/s: 3.0.0-beta2
> Implement a peek method for the sorted index cursor
> ----------------------------------------------------
>
> Key: IGNITE-18243
> URL: https://issues.apache.org/jira/browse/IGNITE-18243
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> The transaction protocol have no possibility to create a range lock. Instead of the range locks, we are using two locks on two consecutive keys. There is a problem: how to determine a next key when we have a current one.
> For looking for the next key, we are planing to use a loop:
> {code:java}
> do {
> nextKey = cursor.peek();
> lock(nextKey);
> } while (nextKey != cursor.peek());
> {code}
> Hence, cursor.peek() should return a next element from the cursor (by sorted index) without movement from current position.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)