[
https://issues.apache.org/jira/browse/PHOENIX-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573719#comment-14573719
]
Hudson commented on PHOENIX-1987:
---------------------------------
SUCCESS: Integrated in Phoenix-master #778 (See
[https://builds.apache.org/job/Phoenix-master/778/])
PHOENIX-1987 SIGN built-in function should be order preserving (Shuxiong Ye)
(jamestaylor: rev 47466e317db72d651c120b1c04bf687abfe10e34)
*
phoenix-core/src/main/java/org/apache/phoenix/expression/function/SignFunction.java
* phoenix-core/src/test/java/org/apache/phoenix/expression/SignFunctionTest.java
> SIGN built-in function should be order preserving
> -------------------------------------------------
>
> Key: PHOENIX-1987
> URL: https://issues.apache.org/jira/browse/PHOENIX-1987
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: Shuxiong Ye
> Fix For: 5.0.0, 4.5.0, 4.4.1
>
> Attachments:
> 0001-PHOENIX-1987-SIGN-built-in-function-should-be-order_v2.patch
>
>
> The SIGN built-in function preserves the order of its input. This needs to be
> explicitly implemented in SignFunction by implementing the following method:
> {code}
> public OrderPreserving preservesOrder() {
> return OrderPreserving.YES;
> }
> {code}
> This will allow certain optimizations reducing the amount of memory and/or
> buffering that is required if SIGN is used in a GROUP BY or ORDER BY clause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
