[jira] [Comment Edited] (HBASE-13497) Remove MVCC stamps from HFile when that is safe

["Anoop Sam John (JIRA)" <ji...@apache.org>]

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

Anoop Sam John edited comment on HBASE-13497 at 7/30/15 4:37 PM:
-----------------------------------------------------------------

[~larsh]
{quote}
// When all MVCC readpoints are 0, don't write them.
...........
fd.maxMVCCReadpoint >= 0,
Do we need >= or > only?
{quote}
Seems this comment was not addressed while commit. :-)   Pls see HBASE-14173.  Let us commit the change in HBASE-14173.



was (Author: anoop.hbase):
[~larsh]
{quote}
{quote}
// When all MVCC readpoints are 0, don't write them.
...........
fd.maxMVCCReadpoint >= 0,
{quote}
Do we need >= or > only?
{quote}
Seems this comment was not addressed while commit. :-)   Pls see HBASE-14173.  Let us commit the change in HBASE-14173.


> Remove MVCC stamps from HFile when that is safe
> -----------------------------------------------
>
>                 Key: HBASE-13497
>                 URL: https://issues.apache.org/jira/browse/HBASE-13497
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Scanners
>            Reporter: Lars Hofhansl
>            Assignee: Lars Hofhansl
>              Labels: performance
>             Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.1
>
>         Attachments: 13497.txt
>
>
> See discussion in HBASE-13389.
> The optimization was initially put in with HBASE-8166, HBASE-12600 undoes it, this will partially restores it.
> Instead of checking the MVCC readpoints against the oldest current scanner, we check that all are 0, if so, we do not need to write them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)