phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-3667) Optimize BooleanExpressionFilter for tables with encoded columns
Date Sat, 18 Feb 2017 07:22:44 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15873027#comment-15873027
] 

James Taylor commented on PHOENIX-3667:
---------------------------------------

Good point. For columns that are projected, but not referenced in the where clause, I think
we'd need to return NEXT_COL.

> Optimize BooleanExpressionFilter for tables with encoded columns
> ----------------------------------------------------------------
>
>                 Key: PHOENIX-3667
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3667
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Samarth Jain
>
> The client side of Phoenix determines the subclass of BooleanExpressionFilter we use
based on how many column families and column qualifiers are being referenced. The idea is
to minimize the lookup cost during filter evaluation. For encoded columns, instead of using
a Map or Set, we can create a few new subclasses of BooleanExpressionFilter that use an array
instead. No need for any lookups or equality checks - just fill in the position based on the
column qualifier value instead. Since filters are applied on every row between the start/stop
key, this will improve performance quite a bit.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message