Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 14 Dec 2011 09:52:31 +0000 (UTC)
From: "Nicolas Spiegelberg (Created) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2078242437.10395.1323856351448.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (HBASE-5021) Enforce upper bound on timestamp
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Enforce upper bound on timestamp
--------------------------------

                 Key: HBASE-5021
                 URL: https://issues.apache.org/jira/browse/HBASE-5021
             Project: HBase
          Issue Type: Improvement
            Reporter: Nicolas Spiegelberg
            Assignee: Nicolas Spiegelberg
            Priority: Critical
             Fix For: 0.94.0


We have been getting hit with performance problems on our time-series database due to invalid timestamps being inserted by the timestamp.  We are working on adding proper checks to app server, but production performance could be severely impacted with significant recovery time if something slips past.  Since timestamps are considered a fundamental part of the HBase schema & multiple optimizations use timestamp information, we should allow the option to sanity check the upper bound on the server-side in HBase.

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