[
https://issues.apache.org/jira/browse/HBASE-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276082#comment-13276082
]
Anil Gupta commented on HBASE-5999:
-----------------------------------
Hi Zhihong,
I have got the fix for it and I discussed my fix with Ted Yu and he seemed ok
with that. I just need to create a patch. Please refer to user mailing list
discussion between me and Ted.
Essentially this is the change required in validateParameter method in
AggregationClient class:
if (scan == null || (Bytes.equals(scan.getStartRow(), scan.getStopRow()) &&
!Bytes.equals(scan.getStartRow(), HConstants.EMPTY_START_ROW)) ||
(Bytes.compareTo(scan.getStartRow(), scan.getStopRow()) > 0 &&
!Bytes.equals(scan.getStopRow(), HConstants.EMPTY_END_ROW) ))
!Bytes.equals(scan.getStopRow(), HConstants.EMPTY_END_ROW) is the additional
condition required to handle this case. I have tested my code and it works
fine. Please let me know if this solution is not right.
Thanks,
Anil Gupta
> 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
