phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-4296) Dead loop in HBase reverse scan when amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE
Date Sun, 05 May 2019 11:49:00 GMT


Hadoop QA commented on PHOENIX-4296:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against 4.x-HBase-1.2 branch at commit bb1327ef89fb0844094470ada74cbe5071b43a0d.
  ATTACHMENT ID: 12967861

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 release audit{color}.  The applied patch generated 6 release audit warnings
(more than the master's current 0 warnings).

    {color:red}-1 lineLengths{color}.  The patch introduces the following lines longer than
    +    protected ChunkedResultIterator(ParallelIteratorFactory delegateIteratorFactory,
MutationState mutationState,
+                = new SpoolingResultIterator.SpoolingResultIteratorFactory(pconn.getQueryServices());

     {color:red}-1 core tests{color}.  The patch failed these unit tests:

Test results:
Release audit warnings:
Console output:

This message is automatically generated.

> Dead loop in HBase reverse scan when amount of scan data is greater than SCAN_RESULT_CHUNK_SIZE
> -----------------------------------------------------------------------------------------------
>                 Key: PHOENIX-4296
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.6.0
>            Reporter: rukawakang
>            Priority: Major
>             Fix For: 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.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

View raw message