[
https://issues.apache.org/jira/browse/PHOENIX-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208666#comment-14208666
]
Brian Johnson commented on PHOENIX-1439:
----------------------------------------
Phoenix 4.1.0 and HBase 0.98.5. The real problem was that as we increased the
number of LIKEs (100 or more) the performance dropped off substantially. It was
also affected by the number of records, but that shouldn't be the case with
skip scan because it's indexed. It should be on the order of the number of
seeks, not the number of records. When we switched over to BETWEEN performance
was on par with our expectations.
> LIKE doesn't appear to use skip scanning
> ----------------------------------------
>
> Key: PHOENIX-1439
> URL: https://issues.apache.org/jira/browse/PHOENIX-1439
> Project: Phoenix
> Issue Type: Improvement
> Reporter: Brian Johnson
>
> We had a query using several like statements of the form LIKE 'prefix|%' and
> LIKE 'prefix2|%' ... and the performance was on par with a full table scan.
> When we replaced it with BETWEEN 'prefix|' and 'prefix|FFFFFFF...' the query
> time was substantially faster. It seems that the LIKE query should work with
> skip scan, but I don't think it's being used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
