[
https://issues.apache.org/jira/browse/PHOENIX-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890957#comment-13890957
]
James Taylor commented on PHOENIX-18:
-------------------------------------
Thanks for the quick work on this one, [~anoop.hbase]. Would you mind
summarizing what the bug is? I see that your caching the Object version as well
as the byte[] version of the aggregated value now. Lars was right that the
original query should not have had single quotes around the alias reference as
otherwise the ORDER BY would have been sorting based on a constant value (and
would have been optimized out). Are you saying that even if the alias was
referenced correctly, that these would have failed (i.e. your new tests would
fail)?
Might be worth spinning up a pull request on our mirror for this one.
> (count(distinct col)) DESC sort process not working
> ----------------------------------------------------
>
> Key: PHOENIX-18
> URL: https://issues.apache.org/jira/browse/PHOENIX-18
> Project: Phoenix
> Issue Type: Bug
> Environment: Cloudera 4.5
> Reporter: saravanan
> Assignee: Anoop Sam John
> Attachments: PHOENIX-18.patch
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> I run the below query and not getting the expected result...
> SELECT "tbp__VPN" as "Part Number",Count(distinct "tbp__EGN") as "egn Number"
> FROM "AL_V_PNO_DEMO" WHERE ("tbp__VPN" is not null) GROUP BY "tbp__VPN" ORDER
> BY 'egn Number' DESC /* +SKIP_SCAN */;
> the above query executes fine but the sorting is not done for ORDER BY
> column..Is its problem with the Query or Its some Bug in Phoenix.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
