You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zhihong Yu (JIRA)" <ji...@apache.org> on 2012/05/15 19:46:39 UTC

[jira] [Commented] (HBASE-5999) AggregationClient throws an exception when startRow is set and stopRow is not set in scan object.

    [ https://issues.apache.org/jira/browse/HBASE-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276045#comment-13276045 ] 

Zhihong Yu commented on HBASE-5999:
-----------------------------------

I think we can relax the original constraint by checking scan.hasFilter()
If a filter is present, there is no need to set stopRow.
                
> AggregationClient throws an exception when startRow is set and stopRow is not set in scan object.
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5999
>                 URL: https://issues.apache.org/jira/browse/HBASE-5999
>             Project: HBase
>          Issue Type: Bug
>          Components: client, coprocessors
>    Affects Versions: 0.92.0, 0.92.1
>            Reporter: Anil Gupta
>            Priority: Minor
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> AggregationClient throws an exception when the startRow is set and stopRow is not set in scan object. AggregationClient should not throw the exception in this case because the user might want to scan the entire table starting from the startRow.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira