You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2014/03/16 08:21:23 UTC

[jira] [Resolved] (PHOENIX-293) Support BINARY and VARBINARY

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

Gabriel Reid resolved PHOENIX-293.
----------------------------------

    Resolution: Fixed

Bulk resolve of closed issues imported from GitHub. This status was reached by first re-opening all closed imported issues and then resolving them in bulk.

> Support BINARY and VARBINARY
> ----------------------------
>
>                 Key: PHOENIX-293
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-293
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: James Taylor
>            Assignee: tonyhuang
>
> We currently support BINARY, but this is actually mislabeled and should actually be called VARBINARY. We should switch this name (adding a check on the deserialization of a PTable to switch the sql type code if no max length column is present). Then we should add support for BINARY(x) which is a fixed length binary. We can allow this to occur anywhere in the PK, unlike VARBINARY which may only be at the end of the PK.



--
This message was sent by Atlassian JIRA
(v6.2#6252)