[
https://issues.apache.org/jira/browse/PHOENIX-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14717338#comment-14717338
]
James Taylor edited comment on PHOENIX-2214 at 8/27/15 7:25 PM:
----------------------------------------------------------------
Yes, that's true, if k1 is bound by an equality constraint. That's PHOENIX-2194.
was (Author: jamestaylor):
Yes, that's try, if k1 is bound by an equality constraint. That's PHOENIX-2194.
> ORDER BY optimization incorrect for queries over views containing WHERE clause
> ------------------------------------------------------------------------------
>
> Key: PHOENIX-2214
> URL: https://issues.apache.org/jira/browse/PHOENIX-2214
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.5.1
> Reporter: Eli Levine
> Attachments:
> 0001-Test-case-to-outline-issue-with-view-ORDER-BY-optimi.patch
>
>
> Phoenix optimizes away ORDER BY clauses if they are the same order as the
> default PK order. However, this optimization is not done correctly for views
> (tenant-specific and regular) if the view has been created with a WHERE
> clause.
> See attached patch for repro, in which the last assertEquals() fails due to
> the fact that ORDER BY is not optimized away, as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
