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 2014/02/26 01:20:25 UTC

[jira] [Created] (PHOENIX-76) Fix perf regression due to PHOENIX-29

James Taylor created PHOENIX-76:
-----------------------------------

             Summary: Fix perf regression due to PHOENIX-29
                 Key: PHOENIX-76
                 URL: https://issues.apache.org/jira/browse/PHOENIX-76
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 3.0.0
            Reporter: James Taylor
            Assignee: Anoop Sam John
             Fix For: 3.0.0


Many queries got slower as a result of PHOENIX-29. There are a few simple checks we can do to prevent the adding of the new filter:
- if the query is an aggregate query, as we don't return KVs in this case, so we're only doing extra processing that we don't need. For this, you can check statement.isAggregate().
- if there are multiple column families  referenced in the where clause, as the seek that gets done is better in this case because we'd potentially be seeking over an entire stores worth of data into a different store.




--
This message was sent by Atlassian JIRA
(v6.1.5#6160)