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

Hudson commented on PHOENIX-4296:
---------------------------------

ABORTED: Integrated in Jenkins build Phoenix-4.x-HBase-1.3 #404 (See 
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.3/404/])
PHOENIX-4296: reverse scan in ChunkedResultIterator (tdsilva: rev 
1d99ff049807ce98bc4a831eeb219e793f705793)
* (add) 
phoenix-core/src/test/java/org/apache/phoenix/iterate/ChunkedResultIteratorTest.java
* (edit) 
phoenix-core/src/main/java/org/apache/phoenix/iterate/ChunkedResultIterator.java


> Dead loop in HBase reverse scan when amount of scan data is greater than 
> SCAN_RESULT_CHUNK_SIZE
> -----------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4296
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4296
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: rukawakang
>            Assignee: Chen Feng
>            Priority: Major
>             Fix For: 4.15.0, 5.1.0, 4.14.2
>
>         Attachments: PHOENIX-4296-4.x-HBase-1.2-v2.patch, 
> PHOENIX-4296-4.x-HBase-1.2-v3.patch, PHOENIX-4296-4.x-HBase-1.2-v4.patch, 
> PHOENIX-4296-4.x-HBase-1.2.patch, PHOENIX-4296.patch
>
>
> This problem seems to only occur with reverse scan not forward scan. When 
> amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE(default 2999), 
> Class ChunkedResultIteratorFactory will multiple calls function 
> getResultIterator. But in function getResultIterator it always readjusts 
> startRow, in fact, if in reverse scan we should readjust stopRow. For example 
> {code:java}
> if (ScanUtil.isReversed(scan)) {
>     scan.setStopRow(ByteUtil.copyKeyBytesIfNecessary(lastKey));
> } else {
>     scan.setStartRow(ByteUtil.copyKeyBytesIfNecessary(lastKey));
> }
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to