[
https://issues.apache.org/jira/browse/IGNITE-18925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Tupitsyn updated IGNITE-18925:
------------------------------------
Description:
IGNITE-17636 removes BinaryTuple conversion when sending data from storage to
client.
This ticket is about sending data from client to storage: we read it as
*BinaryTuple*, then convert to Tuple, then *RowAssembler* converts it back to
*BinaryTuple*. Get rid of this unnecessary conversion.
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 engine adopts BinaryTuple, we will be able to avoid conversion and
perform a byte-for-byte copy to the client socket.
> Thin 3.0: Avoid BinaryTuple conversion from client to storage
> -------------------------------------------------------------
>
> Key: IGNITE-18925
> URL: https://issues.apache.org/jira/browse/IGNITE-18925
> Project: Ignite
> Issue Type: Task
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-92, ignite-3
>
> IGNITE-17636 removes BinaryTuple conversion when sending data from storage to
> client.
> This ticket is about sending data from client to storage: we read it as
> *BinaryTuple*, then convert to Tuple, then *RowAssembler* converts it back to
> *BinaryTuple*. Get rid of this unnecessary conversion.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
