Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
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.
