You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (Jira)" <ji...@apache.org> on 2021/05/06 16:48:00 UTC
[jira] [Commented] (IGNITE-13670) Skip writing null-map and varlen
table when possible.
[ https://issues.apache.org/jira/browse/IGNITE-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17340311#comment-17340311 ]
Taras Ledkov commented on IGNITE-13670:
---------------------------------------
[~amashenkov], the patch is OK with me.
> Skip writing null-map and varlen table when possible.
> -----------------------------------------------------
>
> Key: IGNITE-13670
> URL: https://issues.apache.org/jira/browse/IGNITE-13670
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: iep-54, ignite-3, newbie
> Time Spent: 10m
> Remaining Estimate: 0h
>
> h3. Motivation.
> The nullmap is currently always written to the tuple layout for all columns
> even if there are no nullable columns described in the schema.
> The same is true and can be done for varlen table.
> Seems, we can extend this idea to every single tuple and still have the ability to compare key/value content fast as byte arrays.
> Apparently, this will work for rows of same schema version, but we shouldn't bother about the schema version,
> because anyway, old row will be upgraded to the newer version before comparison according to the live-schema concept.
> h3. Description.
> Let's skip an empty nullmap and write just a flag instead.
> Let's skip an empty varlen table and write just a flag instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)