Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <817786737.1245556807725.JavaMail.jira@brutus>
Date: Sat, 20 Jun 2009 21:00:07 -0700 (PDT)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-1558) deletes use
 'HConstants.LATEST_TIMESTAMP' but no one translates that into 'now'
In-Reply-To: <1137039584.1245555847777.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ryan rawson updated HBASE-1558:
-------------------------------

    Description: Deletes don't update MAX_TIMESTAMP -> now like puts do.  (was: This one is huge guys, when you are deleting columns or families, the Delete uses "Long.MAX_VALUE" but no one translates it into 'System.currentTimeMillis()'.  Same for Puts.  It's a wonder anything works actually!

The question is: should the client set the TS to 'now' or the server?  My guess is the server....)
        Summary: deletes use 'HConstants.LATEST_TIMESTAMP' but no one translates that into 'now'  (was: add/delete use 'HConstants.LATEST_TIMESTAMP' but no one translates that into 'now')

> deletes use 'HConstants.LATEST_TIMESTAMP' but no one translates that into 'now'
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-1558
>                 URL: https://issues.apache.org/jira/browse/HBASE-1558
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client, regionserver
>    Affects Versions: 0.20.0
>            Reporter: ryan rawson
>            Priority: Blocker
>             Fix For: 0.20.0
>
>
> Deletes don't update MAX_TIMESTAMP -> now like puts do.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.