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/05/23 03:10:00 UTC

[jira] [Updated] (IGNITE-19542) .NET: Thin 3.0: Refactor IgniteTuple to wrap BinaryTuple

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

Pavel Tupitsyn updated IGNITE-19542:
------------------------------------
    Labels: .NET ignite-3  (was: )

> .NET: Thin 3.0: Refactor IgniteTuple to wrap BinaryTuple
> --------------------------------------------------------
>
>                 Key: IGNITE-19542
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19542
>             Project: Ignite
>          Issue Type: Task
>          Components: platforms, thin client
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Major
>              Labels: .NET, ignite-3
>             Fix For: 3.0.0-beta2
>
>
> * Client protocol uses *BinaryTuple* to exchange data (IGNITE-17297)
> * When reading data from server, currently we unpack all elements of the incoming *BinaryTuple* into *IgniteTuple*
> This is extra work and extra allocations. Instead, wrap the incoming *BinaryTuple* like *MutableRowTupleAdapter* does in Java.



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