You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2023/05/04 17:52:00 UTC
[jira] [Commented] (IGNITE-19302) Phantom reads protection is broken
[ https://issues.apache.org/jira/browse/IGNITE-19302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719455#comment-17719455 ]
Roman Puchkovskiy commented on IGNITE-19302:
--------------------------------------------
Sorry, I forgot to do it timely: LGTM!
> Phantom reads protection is broken
> ----------------------------------
>
> Key: IGNITE-19302
> URL: https://issues.apache.org/jira/browse/IGNITE-19302
> Project: Ignite
> Issue Type: Bug
> Reporter: Ivan Bessonov
> Assignee: Ivan Bessonov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {{SortedIndexLocker#acquireLockNextKey}} is poorly implemented and not tested properly. It ignores the documented contract of {{hasNext}} and {{peek}} from {{{}PeekCursor{}}}.
> "Has next" checks must essentially be replaced with {{{}peek() != null{}}}.
> Unit tests, that would simulate concurrent operations, or maybe even do concurrent operations, must be implemented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)