You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Aleksandr Polovtsev (Jira)" <ji...@apache.org> on 2025/10/21 14:04:00 UTC

[jira] [Updated] (IGNITE-26793) Store log index and term explicitly

     [ https://issues.apache.org/jira/browse/IGNITE-26793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksandr Polovtsev updated IGNITE-26793:
-----------------------------------------
    Description: 
Currently log index and term are stored as a part of the segment file payload. This is inconvenient, because, for example, during recovery we want to read the log index value, but not the whole payload. It is proposed to amend the segment file format to store each entry's index and term explicitly (possible varlen-encoded) before the payload.

Removal of the index and term from the actual payload will be targeted in a different ticket.

> Store log index and term explicitly
> -----------------------------------
>
>                 Key: IGNITE-26793
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26793
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Aleksandr Polovtsev
>            Assignee: Aleksandr Polovtsev
>            Priority: Major
>              Labels: ignite-3
>
> Currently log index and term are stored as a part of the segment file payload. This is inconvenient, because, for example, during recovery we want to read the log index value, but not the whole payload. It is proposed to amend the segment file format to store each entry's index and term explicitly (possible varlen-encoded) before the payload.
> Removal of the index and term from the actual payload will be targeted in a different ticket.



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