[jira] [Commented] (IGNITE-17636) Thin 3.0: Avoid BinaryTuple conversion in client handler

["Igor Sapego (Jira)" <ji...@apache.org>]

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

Igor Sapego commented on IGNITE-17636:
--------------------------------------

Left a minor comment, but looks good in general.

> Thin 3.0: Avoid BinaryTuple conversion in client handler
> --------------------------------------------------------
>
>                 Key: IGNITE-17636
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17636
>             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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> IGNITE-17297 changes thin client protocol to use Binary Tuple (IEP-92) to transfer tuples and rows.
> However, a conversion from Tuple to BinaryTuple and back is performed on every step.
> Once storage engine adopts BinaryTuple, we will be able to avoid conversion and perform a byte-for-byte copy to the client socket.



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