You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Spiegelberg (Commented) (JIRA)" <ji...@apache.org> on 2011/12/14 10:56:31 UTC

[jira] [Commented] (HBASE-5021) Enforce upper bound on timestamp

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

Nicolas Spiegelberg commented on HBASE-5021:
--------------------------------------------

Note: my original idea was to allow the user to input a specified timerange to perform min/max checks.  This doesn't seem to be very useful because the lower bound is already handled by the TTL option.
                
> 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