[
https://issues.apache.org/jira/browse/HBASE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359011#comment-14359011
]
Nick Dimiduk commented on HBASE-13190:
--------------------------------------
I believe the REST code is UTF-8 through-and-through. I think it would be
better to introduce a RegexBinaryComparator. Or perhaps have a single
RegexComparator that consolidates functionality and we can deprecate the old
StringComparator.
[~apurtell], [~avandana] thoughts?
> REST RegexStringComparator should support setCharset
> ----------------------------------------------------
>
> Key: HBASE-13190
> URL: https://issues.apache.org/jira/browse/HBASE-13190
> Project: HBase
> Issue Type: Improvement
> Components: REST
> Reporter: Serhiy Bilousov
> Priority: Blocker
>
> 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 .
> 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)
