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

Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2023/04/03 06:32:00 UTC

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

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

Pavel Tupitsyn edited comment on IGNITE-18922 at 4/3/23 6:31 AM:
-----------------------------------------------------------------

*AsyncResultSetImpl* still uses *List<Object>* to hold row data. There is no *BinaryTuple*.

Blocked by IGNITE-17684 - postponing.


was (Author: ptupitsyn):
*AsyncResultSetImpl* still uses *List<Object>* to hold row data. There is no *BinaryTuple*.

> 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)