[ https://issues.apache.org/jira/browse/HBASE-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454503#comment-13454503 ]
Jean-Daniel Cryans commented on HBASE-5021: ------------------------------------------- Since this commit we don't report NoSuchColumnFamilyException on multi() calls, I opened HBASE-6769. > 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 > > Attachments: 5021-addendum.txt, > ASF.LICENSE.NOT.GRANTED--D849.1.patch, ASF.LICENSE.NOT.GRANTED--D849.2.patch, > ASF.LICENSE.NOT.GRANTED--D849.3.patch, HBASE-5021-trunk.patch > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira