[
https://issues.apache.org/jira/browse/HBASE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393019#comment-14393019
]
Serhiy Bilousov commented on HBASE-13190:
-----------------------------------------
Yes [[email protected]] that one way of doing it or we can have
RegexBinaryComparator what would be just wrapper around RegexComparator (like
in asynchbase) with set thouse parameters (charset, enginetype) by default.
> REST RegexStringComparator should support charset and
> RegexStringComparator.EngineType
> --------------------------------------------------------------------------------------
>
> Key: HBASE-13190
> URL: https://issues.apache.org/jira/browse/HBASE-13190
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Serhiy Bilousov
>
> There is no way to set charset (ISO-8859-1 as recommended) to
> RegexStringComparator through the REST call what make RegexString filter
> unusable for the row key made of arbitrary bytes. It also would be helpful to
> be able to pass RegexStringComparator.EngineType or configure HBase REST with
> default engine.
> This is major blocker in our business case.
> {code:title=ScannerModel.java|borderStyle=solid}
> case RegexStringComparator:
> comparator = new RegexStringComparator(value);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
