[
https://issues.apache.org/jira/browse/IGNITE-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707918#comment-17707918
]
Anton Vinogradov commented on IGNITE-19173:
-------------------------------------------
Unfortunately, a lot of restored BinaryObject's fields are required on put on
backups: typeId, len, hashCode, etc.
And it's still seems to be a proper behaviour that cpu utilisation (on
restoration) is requred on put to have the data transformed in memory and
during the transfering over the network.
So, closing as `won't fix`.
> Get rid BinaryObject restoration on backups during the put operations
> ---------------------------------------------------------------------
>
> Key: IGNITE-19173
> URL: https://issues.apache.org/jira/browse/IGNITE-19173
> Project: Ignite
> Issue Type: Improvement
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: iep-97
>
> Currently, array restoration is necessary on backups on put operation because
> typeId is required to wait for the proper metadata.
> But, typeId can be send (on put) separately to avoid useless restoration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
