You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars George (JIRA)" <ji...@apache.org> on 2012/06/25 13:17:42 UTC
[jira] [Created] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Lars George created HBASE-6265:
----------------------------------
Summary: 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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Attachment: HBASE-6265.patch
Patch adds test and fix.
> 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
> Assignee: Lars George
> Attachments: 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404944#comment-13404944 ]
Lars George commented on HBASE-6265:
------------------------------------
Just as a comment, the two -1's from Hadoop QA are bogus. The Javac test simply counts the occurrences of lines starting with "Warning", which in this case has one more but unrelated to the patch.
As for the Findbugs, this is stuck with the file tracking the expected findbugs warnings not being updated. All the recent builds have the same -1.
We should create an issue to fix those two deficiencies in the QA script.
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404459#comment-13404459 ]
Lars George commented on HBASE-6265:
------------------------------------
What are your thoughts on applying this to anything >= 0.92? This can affect anyone using coprocessors and asking for a timestamp in a prePut(). Seems severe enough. Let me know and apply to all heads in branches accordingly.
> 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.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Status: Patch Available (was: Open)
Patch v2 initializes the KV properly to trigger the expected code path.
> 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.94.0, 0.92.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404470#comment-13404470 ]
Hadoop QA commented on HBASE-6265:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12534100/HBASE-6265.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 failed these unit tests:
org.apache.hadoop.hbase.TestKeyValue
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2300//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2300//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2300//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2300//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
[jira] [Assigned] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George reassigned HBASE-6265:
----------------------------------
Assignee: Lars George
> 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
> Assignee: Lars George
> Attachments: 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Attachment: HBASE-6265-v2.patch
Patch v2 fixes test to properly set the new time.
> 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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Status: Patch Available (was: Open)
Adds a proper long type indicator.
> 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.94.0, 0.92.0, 0.96.0
> Reporter: Lars George
> Assignee: Lars George
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404508#comment-13404508 ]
Zhihong Ted Yu commented on HBASE-6265:
---------------------------------------
+1 on patch v2.
> 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400585#comment-13400585 ]
Zhihong Ted Yu commented on HBASE-6265:
---------------------------------------
Sounds good to me.
A new test case would be nice to show this problem.
> 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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6265:
----------------------------------
Priority: Critical (was: Major)
+1 and raise priority due to the potential for bad surprises.
> 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
> Priority: Critical
> 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404868#comment-13404868 ]
Hadoop QA commented on HBASE-6265:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12534169/HBASE-6265-v3.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 7 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 failed these unit tests:
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2307//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2307//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2307//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2307//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
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Fix Version/s: 0.96.0
Affects Version/s: 0.96.0
0.92.0
0.94.0
Status: Patch Available (was: Open)
Trivial test and patch. Please +1 and I'll commit.
> 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.94.0, 0.92.0, 0.96.0
> Reporter: Lars George
> Assignee: Lars George
> Fix For: 0.96.0
>
> Attachments: 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404948#comment-13404948 ]
stack commented on HBASE-6265:
------------------------------
I made hbase-6301 to fix hadoopqa counts.
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Status: Open (was: Patch Available)
> 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.94.0, 0.92.0, 0.96.0
> Reporter: Lars George
> Assignee: Lars George
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405028#comment-13405028 ]
Hudson commented on HBASE-6265:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #77 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/77/])
HBASE-6265 Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed (Revision 1356106)
Result = FAILURE
larsgeorge :
Files :
* /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/KeyValue.java
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/TestKeyValue.java
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411156#comment-13411156 ]
Hudson commented on HBASE-6265:
-------------------------------
Integrated in HBase-0.94-security #39 (See [https://builds.apache.org/job/HBase-0.94-security/39/])
HBASE-6265 Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed (added CHANGES.txt edit) (Revision 1356124)
HBASE-6265 Calling getTimestamp() on a KV in cp.prePut() causes KV not to be flushed (Revision 1356105)
Result = SUCCESS
larsgeorge :
Files :
* /hbase/branches/0.94/CHANGES.txt
larsgeorge :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/KeyValue.java
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/TestKeyValue.java
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Attachment: HBASE-6265-0.94.patch
HBASE-6265-0.92.patch
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Status: Open (was: Patch Available)
Sorry, had to cancel this patch. I need to fix one more issue with this because the updateTimestamp() is not triggering the reset as expected. Will resubmit shortly, but nevertheless please let me know about where to apply eventually.
> 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.94.0, 0.92.0, 0.96.0
> Reporter: Lars George
> Assignee: Lars George
> Fix For: 0.96.0
>
> Attachments: 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
[jira] [Commented] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13404511#comment-13404511 ]
stack commented on HBASE-6265:
------------------------------
+1 on applying to all versions
> 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
[jira] [Closed] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl closed HBASE-6265.
--------------------------------
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.94.1, 0.96.0
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Fix Version/s: 0.94.1
0.92.2
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Applied patches to the HEAD of all branches listed. Thanks for the review.
> 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
> Priority: Critical
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
> Attachments: HBASE-6265-0.92.patch, HBASE-6265-0.94.patch, HBASE-6265-v2.patch, HBASE-6265-v3.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
[jira] [Updated] (HBASE-6265) Calling getTimestamp() on a KV in
cp.prePut() causes KV not to be flushed
Posted by "Lars George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars George updated HBASE-6265:
-------------------------------
Attachment: HBASE-6265-v3.patch
Adds proper indicator for long value.
> 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
> Priority: Critical
> Fix For: 0.96.0
>
> Attachments: HBASE-6265-v2.patch, HBASE-6265-v3.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