[
https://issues.apache.org/jira/browse/PHOENIX-4972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662790#comment-16662790
]
Lars Hofhansl commented on PHOENIX-4972:
----------------------------------------
FYI. Also tried cost based planning, but in this case it is significantly
overestimating the cost of the hash join (it does seem to realize that it can
rid of an ORDER BY and/or notice the LIMIT)
> ORDER BY should use a GLOBAL index even if the query is not fully covered
> -------------------------------------------------------------------------
>
> Key: PHOENIX-4972
> URL: https://issues.apache.org/jira/browse/PHOENIX-4972
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Lars Hofhansl
> Priority: Minor
> Attachments: PHOENIX-4972-4.x-HBase-1.4--not-working.patch,
> PHOENIX-4972-4.x-HBase-1.4-v1.patch
>
>
> Like PHOENIX-4964 but for global indexes
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
