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

Posted to dev@phoenix.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2014/03/14 06:11:43 UTC

[jira] [Resolved] (PHOENIX-128) Support coercion and descending sort order for ARRAY

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

ramkrishna.s.vasudevan resolved PHOENIX-128.
--------------------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0.0

> Support coercion and descending sort order for ARRAY
> ----------------------------------------------------
>
>                 Key: PHOENIX-128
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-128
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: ramkrishna.s.vasudevan
>             Fix For: 3.0.0, 4.0.0
>
>         Attachments: Phoenix-128_1.patch, Phoenix-128_2.patch, Phoenix-128_3.patch, Phoenix-128_4.patch, Phoenix-128_5.patch
>
>
> Now that our ARRAY types may be used in the primary key, we need to support descending sort order (i.e. inverting the bits). There are also holes in the support for coerce, as it's legitimate to coerce an array of BIGINT to an array of INTEGER for example.
> This can all be handled pretty easily in the PArrayDataType.coerceBytes() method.



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