[
https://issues.apache.org/jira/browse/PHOENIX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917000#comment-13917000
]
Hudson commented on PHOENIX-76:
-------------------------------
FAILURE: Integrated in Apache Phoenix - Branch:master #89 (See
[https://builds.apache.org/job/Phoenix/89/])
PHOENIX-76 (anoopsamjohn: rev 348b7517ade37b3e8b879899b3b3a3729efcb63a)
*
phoenix-core/src/main/java/org/apache/phoenix/filter/ColumnProjectionFilter.java
* phoenix-core/src/main/java/org/apache/phoenix/iterate/ParallelIterators.java
PHOENIX-76 (anoopsamjohn: rev 2ca85ab681f3080e52db632b1a78d45445fd9cea)
* phoenix-core/src/main/java/org/apache/phoenix/iterate/ParallelIterators.java
> 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
>
> Attachments: PHOENIX-76.patch
>
>
> 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)
