[
https://issues.apache.org/jira/browse/PHOENIX-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-3442:
----------------------------------
Description:
Comments from [~jamestaylor]:
The way we differentiate a null value now is by the value being an empty byte
array (explicitly set to null) versus not being present (in which case we use
the default value).
This is encapsulated in the DefaultValueExpression.
We'll need to tweak our encoding for this.
One way would be to use a negative number for the offset.
Summary: Support null when columns have default values for immutable
tables with encoding scheme COLUMNS_STORED_IN_SINGLE_CELL (was: Support
default values for immutable tables with encoding scheme
COLUMNS_STORED_IN_SINGLE_CELL)
> Support null when columns have default values for immutable tables with
> encoding scheme COLUMNS_STORED_IN_SINGLE_CELL
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-3442
> URL: https://issues.apache.org/jira/browse/PHOENIX-3442
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Samarth Jain
>
> Comments from [~jamestaylor]:
> The way we differentiate a null value now is by the value being an empty byte
> array (explicitly set to null) versus not being present (in which case we use
> the default value).
> This is encapsulated in the DefaultValueExpression.
> We'll need to tweak our encoding for this.
> One way would be to use a negative number for the offset.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
