You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/06/08 21:01:03 UTC
[jira] [Commented] (PHOENIX-1032) Don't compile alternate plans if
query is a point lookup
[ https://issues.apache.org/jira/browse/PHOENIX-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021268#comment-14021268 ]
Hudson commented on PHOENIX-1032:
---------------------------------
SUCCESS: Integrated in Phoenix | 3.0 | Hadoop1 #111 (See [https://builds.apache.org/job/Phoenix-3.0-hadoop1/111/])
PHOENIX-1032 Don't compile alternate plans if query is a point lookup (jtaylor: rev bf395def638b12fb07c5843616d8d2d34428435b)
* 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)