[
https://issues.apache.org/jira/browse/IGNITE-21019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-21019:
--------------------------------------
Fix Version/s: 3.0.0-beta2
> Sql. Improve conversion to BinaryRow in UpdatableTableImpl
> ----------------------------------------------------------
>
> Key: IGNITE-21019
> URL: https://issues.apache.org/jira/browse/IGNITE-21019
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As for now, {{UpdatableTableImpl}} uses {{RowAssembler}} to re-assemble row
> prior to send it to the table. The problem here is this is not very efficient
> because of number of reasons. First, the most simple constructor of
> {{RowAssembler}} is used, this causes tuple builder to preallocate 4kb of
> buffer, which sometimes is too much. Second, usage of {{RowAssembler}}
> implies double (de-)serialization since every field should be read from
> source row and write back to target tuple.
> Given that sql row now natively supports to binary tuple conversion,
> depending on the schema of a table we may reuse that binary tuple or
> reshuffle fields avoiding deserialisation by reading raw bytes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
