Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 3 Jul 2017 09:05:00 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13083513.1498754576000.157752.1499072700130@Atlassian.JIRA>
In-Reply-To: <JIRA.13083513.1498754576000@Atlassian.JIRA>
References: <JIRA.13083513.1498754576000@Atlassian.JIRA> <JIRA.13083513.1498754576466@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-18295)  The result contains the cells
 across different rows
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 03 Jul 2017 09:05:07 -0000


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

ramkrishna.s.vasudevan commented on HBASE-18295:
------------------------------------------------

bq.It is hard to say that the we need the change to apply in all places.
I do feel atleast below
{code}
} else if (qcode == ScanQueryMatcher.MatchCode.INCLUDE_AND_SEEK_NEXT_COL) {
            seekOrSkipToNextColumn(cell);
          } else {
            this.heap.next();
          }
{code}
we need the change because we are seeking to nextcol and if there is a chance we move to next row we will have similar issues. Else patch looks good to me. 


>  The result contains the cells across different rows
> ----------------------------------------------------
>
>                 Key: HBASE-18295
>                 URL: https://issues.apache.org/jira/browse/HBASE-18295
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Blocker
>             Fix For: 3.0.0, 1.4.0, 1.3.2, 2.0.0-alpha-2
>
>         Attachments: HBASE-18295.branch-1.3.v0.patch, HBASE-18295.branch-1.v0.patch, HBASE-18295.v0.patch, HBASE-18295.v1.patch
>
>
> From the [flaky dashboard|https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html]
> If we use the cell which won't be flushed into disk as the top cell to reopen the scanners, the new top cell will change. If the new top cell is in different row, the matcher will reset, and then matcher will accept the new top cell...
> The TestStore# testFlushBeforeCompletingScan reproduces the bug.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)