[
https://issues.apache.org/jira/browse/HBASE-14928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041907#comment-15041907
]
Jerry He commented on HBASE-14928:
----------------------------------
I wonder if it is fine to go back to the old behavior completely.
In the new code,
{code}
@Path("{suffixglobbingspec: .*\\*/.+}")
{code}
{code}
@Path("{scanspec: .*[*]$}")
{code}
The url path table/rowkey* will be handled by the scanspec. Should it be
handled by the suffixglobbingspec? Notice that the suffixglobbingspec needs
table/rowkey*/column
The workaround I had is to table/rowkey*/family1. Then it would go back to the
old behavior.
> Start row should be set for query through HBase REST gateway involving
> globbing option
> --------------------------------------------------------------------------------------
>
> Key: HBASE-14928
> URL: https://issues.apache.org/jira/browse/HBASE-14928
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 2.0.0, 1.2.0, 1.3.0, 1.1.3, 0.98.17
>
> Attachments: 14928-v1.txt
>
>
> As Ben Sutton reported in the thread, Slow response on HBase REST api using
> globbing option, query through the Rest API with a globbing option i.e.
> http://<HBase_Rest>:<HBase_Rest_Port>/table/key\* executes extremely slowly.
> Jerry He pointed out that PrefixFilter is used for query involving globbing
> option.
> This issue is to fix this bug by setting start row for such queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
