[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed

["Lars George (JIRA)" <ji...@apache.org>]

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

Lars George commented on HBASE-6265:
------------------------------------

I think one easy non-intrusive fix is to reset the timestampCache variable on calling updateLatestStamp(). If you agree I would provide a patch doing that?
                
> 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
>            Reporter: Lars George
>
> 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