[
https://issues.apache.org/jira/browse/HBASE-13190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14393004#comment-14393004
]
Andrew Purtell commented on HBASE-13190:
----------------------------------------
Maybe I'm missing something. RegexStringComparator has a setCharset() method
that lets you specify what charset to use when converting binary data to a
string for comparison. The default is UTF-8. So maybe we just need to add
support to REST for setting this option? That would probably be an update to
ParseFilter.
> 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)
