[jira] [Updated] (IGNITE-23348) Add timestamp to Metastorage Entry

["Kirill Tkalenko (Jira)" <ji...@apache.org>]

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

Kirill Tkalenko updated IGNITE-23348:
-------------------------------------
    Description: 
In order for us to be able to safely change the behavior of methods from IGNITE-23307, we need to add the operation timestamp to the *org.apache.ignite.internal.metastorage.Entry*.

Since in IGNITE-23307 methods will start throwing *CompactedException*, and we will be able to get an entry with an already compacted revision (for example, a very old entry), it will be useful for components to leave getting the entry change timestamp. For this we will use +8 bytes, but for metastorage this is not a problem.

  was:In order for us to be able to safely change the behavior of methods from IGNITE-23307, we need to add the operation timestamp to the *org.apache.ignite.internal.metastorage.Entry*.


> Add timestamp to Metastorage Entry
> ----------------------------------
>
>                 Key: IGNITE-23348
>                 URL: https://issues.apache.org/jira/browse/IGNITE-23348
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>
> In order for us to be able to safely change the behavior of methods from IGNITE-23307, we need to add the operation timestamp to the *org.apache.ignite.internal.metastorage.Entry*.
> Since in IGNITE-23307 methods will start throwing *CompactedException*, and we will be able to get an entry with an already compacted revision (for example, a very old entry), it will be useful for components to leave getting the entry change timestamp. For this we will use +8 bytes, but for metastorage this is not a problem.



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