[jira] [Updated] (IGNITE-18922) Thin 3.0: Avoid BinaryTuple conversion in client SQL handler

["Pavel Tupitsyn (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-18922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Tupitsyn updated IGNITE-18922:
------------------------------------
    Description: 
IGNITE-17297 changes thin client protocol to use Binary Tuple (IEP-92) to transfer tuples and rows.

Once SQL engine adopts BinaryTuple, we will be able to avoid conversion and perform a byte-for-byte copy in *ClientSqlCommon.packCurrentPage*.

  was:
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 and SQL engines adopt BinaryTuple, we will be able to avoid conversion and perform a byte-for-byte copy from storage/sql to the client socket.


> Thin 3.0: Avoid BinaryTuple conversion in client SQL handler
> ------------------------------------------------------------
>
>                 Key: IGNITE-18922
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18922
>             Project: Ignite
>          Issue Type: Task
>          Components: thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: iep-92, ignite-3
>
> IGNITE-17297 changes thin client protocol to use Binary Tuple (IEP-92) to transfer tuples and rows.
> Once SQL engine adopts BinaryTuple, we will be able to avoid conversion and perform a byte-for-byte copy in *ClientSqlCommon.packCurrentPage*.



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