hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed
Date Sat, 30 Jun 2012 12:51:43 GMT

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

Hadoop QA commented on HBASE-6265:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12534104/HBASE-6265-v2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    +1 hadoop2.0.  The patch compiles against the hadoop 2.0 profile.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The applied patch generated 5 javac compiler warnings (more than the trunk's
current 4 warnings).

    -1 findbugs.  The patch appears to introduce 6 new Findbugs (version 1.3.9) warnings.

    +1 release audit.  The applied patch does not increase the total number of release audit
warnings.

    +1 core tests.  The patch passed unit tests in .

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2301//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2301//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2301//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2301//console

This message is automatically generated.
                
> Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed
> -------------------------------------------------------------------------
>
>                 Key: HBASE-6265
>                 URL: https://issues.apache.org/jira/browse/HBASE-6265
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.92.0, 0.94.0, 0.96.0
>            Reporter: Lars George
>            Assignee: Lars George
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6265-v2.patch, HBASE-6265.patch
>
>
> There is an issue when you call getTimestamp() on any KV handed into a Coprocessor's
prePut(). It initializes the internal "timestampCache" variable. 
> When you then pass it to the normal processing, the region server sets the time to the
server time in case you have left it unset from the client side (updateLatestStamp() call).

> The TimeRangeTracker then calls getTimestamp() later on to see if it has to include the
KV, but instead of getting the proper time it sees the cached timestamp from the prePut()
call.

--
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

        

Mime
View raw message