[
https://issues.apache.org/jira/browse/IGNITE-13670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-13670:
--------------------------------------
Description:
The nullmap is currently always written to the tuple layout for all columns
(even if there are no nullable columns). This data structure can be further
used to encode default values for non-nullable columns (either a user-specified
value or 0 for primitives).
The bits will still be left unused for non-null non-primitive types (UUID,
String, byte[], etc).
Also, need to add support for skipping writing nullmaps (use the flags bit).
was:
The nullmap is currently always written to the tuple layout for all columns
(even if there are no nullable columns). This data structure can be further
used to encode default values for non-nullable columns (either a user-specified
value or 0 for primitives).
The bits will still be left unused for non-null non-primitive types (UUID,
String, byte[], etc).
> Upgrade nullmap to null-defaults map
> ------------------------------------
>
> Key: IGNITE-13670
> URL: https://issues.apache.org/jira/browse/IGNITE-13670
> Project: Ignite
> Issue Type: Improvement
> Reporter: Alexey Goncharuk
> Priority: Major
> Labels: iep-54, ignite-3
>
> The nullmap is currently always written to the tuple layout for all columns
> (even if there are no nullable columns). This data structure can be further
> used to encode default values for non-nullable columns (either a
> user-specified value or 0 for primitives).
> The bits will still be left unused for non-null non-primitive types (UUID,
> String, byte[], etc).
> Also, need to add support for skipping writing nullmaps (use the flags bit).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
