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 2022/09/09 07:43:00 UTC

[jira] [Commented] (IGNITE-17297) Thin 3.0: Adopt BinaryTuple format in transport layer

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

Igor Sapego commented on IGNITE-17297:
--------------------------------------

[~ptupitsyn] looks good to me.

> Thin 3.0: Adopt BinaryTuple format in transport layer
> -----------------------------------------------------
>
>                 Key: IGNITE-17297
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17297
>             Project: Ignite
>          Issue Type: Improvement
>          Components: platforms, thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: iep-92, ignite-3
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> BinaryTuple (see IEP-92) is a common format for data exchange in Ignite 3. Adopt it in the thin client protocol to be able to avoid intermediate conversions when exchanging data.
> For example, we should be able to write SQL query results to the client socket directly as byte[].
>  
> Update IEP-76 when done.



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