phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-76) Fix perf regression due to PHOENIX-29
Date Thu, 06 Mar 2014 03:47:45 GMT


Anoop Sam John commented on PHOENIX-76:

I can see this issue in closed state.  I will open a new one and attach the patch for the
Hint there?  Or reopen this issue?

> Fix perf regression due to PHOENIX-29
> -------------------------------------
>                 Key: PHOENIX-76
>                 URL:
>             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, patch.diff
> 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

View raw message