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/05/02 09:00:00 UTC

[jira] [Commented] (IGNITE-18925) Thin 3.0: Avoid BinaryTuple conversion from client to storage

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

Igor Sapego commented on IGNITE-18925:
--------------------------------------

Looks good to me.

> Thin 3.0: Avoid BinaryTuple conversion from client to storage
> -------------------------------------------------------------
>
>                 Key: IGNITE-18925
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18925
>             Project: Ignite
>          Issue Type: Task
>          Components: thin client
>    Affects Versions: 3.0.0-beta1
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: iep-92, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> IGNITE-17636 removes BinaryTuple conversion when sending data from storage to client.
> This ticket is about sending data from client to storage: we read it as *BinaryTuple*, then convert to Tuple, then *RowAssembler* converts it back to *BinaryTuple*. Get rid of this unnecessary conversion.



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