You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2016/03/29 02:34:25 UTC
[jira] [Updated] (PHOENIX-2785) Do not store NULLs for immutable
tables
[ https://issues.apache.org/jira/browse/PHOENIX-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated PHOENIX-2785:
-----------------------------------
Attachment: 2785.txt
Simple patch. In addition to not storing nulls or delete markers for immutable tables also fixes the following:
* In removeIfPresent we can break out of the loop when we found the column we're looking for
* Corrects a typing warning
* Reports a ConstraintViolation when null is passed for a non-nullable column (regardless of whether we're storing nulls or not)
> Do not store NULLs for immutable tables
> ---------------------------------------
>
> Key: PHOENIX-2785
> URL: https://issues.apache.org/jira/browse/PHOENIX-2785
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 4.7.0
> Reporter: Lars Hofhansl
> Priority: Minor
> Attachments: 2785.txt
>
>
> Currently we do store Delete markers (or explicit Nulls). For immutable tables that is not necessary. Null is that distinguishable from an absent column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)