[
https://issues.apache.org/jira/browse/PHOENIX-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912712#comment-13912712
]
Anoop Sam John commented on PHOENIX-76:
---------------------------------------
bq.I don't think the essential column family feature works when you use a
FilterList
It will.. When all filters in FL says it is not an essential family the FL also
returns false.
bq. I suppose it depends on how many KV columns are in the CF
Yes it depends on how many KVs in btw 2 columns (which we are interested in) in
a CF. If there are many and it can skip some of the HFile blocks then the
reseek way will give lot of perf boost.
So what do u suggest wrt no# CFs? Condition when we can avoid adding the new
filter way.
> 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)
