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

Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2023/04/11 09:56:00 UTC

[jira] [Commented] (IGNITE-18899) Thin 3.0: Refactor ClientTuple to wrap BinaryTuple similar to MutableRowTupleAdapter

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

Igor Sapego commented on IGNITE-18899:
--------------------------------------

Left few comments.

> Thin 3.0: Refactor ClientTuple to wrap BinaryTuple similar to MutableRowTupleAdapter
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18899
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18899
>             Project: Ignite
>          Issue Type: Improvement
>          Components: thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> * Client protocol uses *BinaryTuple* to exchange data (IGNITE-17297)
> * When reading data from server, currently we unpack all elements of the incoming *BinaryTuple* into *ClientTuple*
> This is extra work and extra allocations. Instead, wrap the incoming *BinaryTuple* like *MutableRowTupleAdapter* does.



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