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

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2015/09/01 00:44:45 UTC

[jira] [Commented] (PHOENIX-2214) ORDER BY optimization incorrect for queries over views containing WHERE clause

    [ https://issues.apache.org/jira/browse/PHOENIX-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14724309#comment-14724309 ] 

James Taylor commented on PHOENIX-2214:
---------------------------------------

Actually, this is a duplicate of PHOENIX-2194, so let me close this one.

> 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)