phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1032) Don't compile alternate plans if query is a point lookup
Date Sun, 08 Jun 2014 19:12:01 GMT

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

Hudson commented on PHOENIX-1032:
---------------------------------

SUCCESS: Integrated in Phoenix | Master | Hadoop1 #247 (See [https://builds.apache.org/job/Phoenix-master-hadoop1/247/])
PHOENIX-1032 Don't compile alternate plans if query is a point lookup (jtaylor: rev 318921eaef93dd5315c144b0f9c22dcf4febabc2)
* phoenix-core/src/main/java/org/apache/phoenix/optimize/QueryOptimizer.java


> Don't compile alternate plans if query is a point lookup
> --------------------------------------------------------
>
>                 Key: PHOENIX-1032
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1032
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>             Fix For: 5.0.0, 3.1, 4.1
>
>         Attachments: PHOENIX-1032.patch
>
>
> We always favor a query plan that resolves to a point lookup. If the query produces a
query plan that is a point lookup for the data table, there's no point in compiling any other
query plans against indexes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message