[
https://issues.apache.org/jira/browse/KYLIN-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203137#comment-15203137
]
liyang edited comment on KYLIN-1504 at 3/20/16 7:23 AM:
--------------------------------------------------------
Thanks Hao! Merged #29 with some revision. Didn't include the PrefixFilter
commit because a) range scan is equally good performance[1]; b) want to keep
the KeyOnlyFilter for reduced traffic.
[1]
http://stackoverflow.com/questions/10942638/should-i-user-prefixfilter-or-rowkey-range-scan-in-hbase
was (Author: liyang.g...@gmail.com):
Thanks Hao! Merged #29 with some revision. Didn't include the PrefixFilter
commit because a) range scan is equally good performance[1]; b) want to keep
the KeyOnlyFilter for reduced traffic.
> Use NavigableSet to store rowkey and use prefix filter to check resource path
> prefix instead String comparison on tomcat side
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: KYLIN-1504
> URL: https://issues.apache.org/jira/browse/KYLIN-1504
> Project: Kylin
> Issue Type: Improvement
> Components: Metadata, REST Service
> Affects Versions: v1.5.0, v1.4.0, v1.3.0
> Reporter: Hao Chen
> Assignee: Hao Chen
> Labels: jobs, metadata
> Fix For: v1.5.1
>
>
> - Use NavigableSet<String> instead of ArrayList<String> to store natively
> ordered and unique row-key instead of ugly repeatedly using
> `Collections.sort` or check whether existing on business logic layer, in fact
> because the raw-key is originally sorted in hbase, the change won't consume
> any more computational complexity.
> - Verify prefix in hbase region level using prefix filter instead of
> comparing String in client side.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
