[jira] [Resolved] (PHOENIX-742) Allow BOOLEAN type to represent NULL

["James Taylor (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PHOENIX-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor resolved PHOENIX-742.
----------------------------------
       Resolution: Won't Fix
    Fix Version/s: 4.1
                   3.1
         Assignee: James Taylor

We allow a BOOLEAN field to be indexed by converting it to a DECIMAL which solves the problem we need. That'll take up two bytes instead of potentially one, but hey, what's an extra byte?

> Allow BOOLEAN type to represent NULL
> ------------------------------------
>
>                 Key: PHOENIX-742
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-742
>             Project: Phoenix
>          Issue Type: Task
>    Affects Versions: 3.0-Release
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 3.1, 4.1
>
>
> As we support BOOLEAN as a first-class citizen data type, we should have a way to serialize/deserialize a NULL value. This will prevent us from having to coerce it back and forth to a DECIMAL when indexed and allow it to be used as a nullable column anywhere in the primary key constraint. We'd need to add a PDataType.isNullable() instead of relying on PDataType.isFixedWidth() to infer whether a nullable column is allowed in the middle of a primary key constraint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)