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/10/07 05:59:00 UTC

[jira] [Commented] (IGNITE-17777) Thin 3.0: use BinaryTuple for Compute and SQL results and arguments

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

Igor Sapego commented on IGNITE-17777:
--------------------------------------

[~ptupitsyn]overall looks good. left few comment.

> Thin 3.0: use BinaryTuple for Compute and SQL results and arguments
> -------------------------------------------------------------------
>
>                 Key: IGNITE-17777
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17777
>             Project: Ignite
>          Issue Type: New Feature
>          Components: thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: iep-92, ignite-3
>             Fix For: 3.0.0-alpha6
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Thin client protocol currently uses MsgPack types to serialize Compute arguments and results, SQL arguments and results.
> This is not consistent with Table API and complicates the protocol.
> All user data in thin client protocol should be serialized in BinaryTuple format.



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