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 2023/01/16 13:49:00 UTC

[jira] [Commented] (IGNITE-18558) Fix Meta Storage prefix reads

    [ https://issues.apache.org/jira/browse/IGNITE-18558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677394#comment-17677394 ] 

Kirill Tkalenko commented on IGNITE-18558:
------------------------------------------

[~apolovtcev] Looks good!

> Fix Meta Storage prefix reads
> -----------------------------
>
>                 Key: IGNITE-18558
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18558
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Aleksandr Polovtcev
>            Assignee: Aleksandr Polovtcev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Meta Storage Manager prefix method implementations use {{KeyCriterion#nextKey}} method to create an upper bound of a prefix. This method is, unfortunately, incorrect, because it adds a 0 to the array, if the last byte overflows. It also uses signed arithmetic, while internal RocksDB implementation uses unsigned.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)