[jira] [Commented] (IGNITE-21230) Improve serialisation of catalog commands

["Ivan Bessonov (Jira)" <ji...@apache.org>]

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

Ivan Bessonov commented on IGNITE-21230:
----------------------------------------

We could port IgniteDataTransferObject from Ignite 2, its serialization format is more efficient and allows for versioning. It's a good compromise between space and speed in my opinion. We don't need maximal compression here, these updates are not too frequent

> Improve serialisation of catalog commands
> -----------------------------------------
>
>                 Key: IGNITE-21230
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21230
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>
> Currently, catalog uses java's built-in serialisation in order to persists descriptors and update entries. Although it is most simple way to address conversion of POJO to byte array, the built-in serialisation is not efficient in terms of occupied space. Given that catalog may contain thousands and thousands of objects, it may result in increased load on a metastorage.
> To address this issue, let's introduce custom serialisation format for catalog's descriptors and update entries.
> NB: we should keep in mind that descriptors may evolve over time, thus we should consider support of versioning for descriptors



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