[
https://issues.apache.org/jira/browse/PHOENIX-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15156170#comment-15156170
]
Lars Hofhansl commented on PHOENIX-2666:
----------------------------------------
The attached v2 patch has:
{code}
private static final int MIN_SEEK_TO_COLUMN_VERSION =
VersionUtil.encodeVersion("0", "94", "12");
{code}
(also checked git, same there)
Note the 94 in there... Pretty sure that's not what you meant :)
Now Phoenix would not use the optimization for any 0.98 version - i.e. this
would be a pretty regression for 0.98 version prior to .12.
> Performance regression: Aggregate query with filter on table with multiple
> column families
> ------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2666
> URL: https://issues.apache.org/jira/browse/PHOENIX-2666
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.7.0
> Reporter: Mujtaba Chohan
> Assignee: James Taylor
> Fix For: 4.7.0
>
> Attachments: PHOENIX-2666.patch, PHOENIX-2666_addendum1.patch,
> PHOENIX-2666_v2.patch
>
>
> In the test, table contains total of 6 columns with one column per column
> family.
> Running a query {code}select count(*) from T where last_column < ?{code} is
> 4x slower after commit for PHOENIX-1312
> (https://git-wip-us.apache.org/repos/asf?p=phoenix.git;a=commit;h=3fdaecdaaa2a2f07070df67f861252fd44e338c3)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
