hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marc Spaggiari (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9905) Enable using seqId as timestamp
Date Thu, 07 Nov 2013 13:29:31 GMT

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

Jean-Marc Spaggiari commented on HBASE-9905:
--------------------------------------------

Is that almost the same thing as what we are discussing here: HBASE-9879 ?

Also, I disagree with deprecating the current mode_mixed. Someone might want to let HBase
decide on the timestamp but might want to be able to take action on a specific cell in the
table based on it's timestamp for later updates.

> Enable using seqId as timestamp 
> --------------------------------
>
>                 Key: HBASE-9905
>                 URL: https://issues.apache.org/jira/browse/HBASE-9905
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Enis Soztutar
>             Fix For: 0.98.0
>
>
> This has been discussed previously, and Lars H. was mentioning an idea from the client
to declare whether timestamps are used or not explicitly. 
> The problem is that, for data models not using timestamps, we are still relying on clocks
to order the updates. Clock skew, same milisecond puts after deletes, etc can cause unexpected
behavior and data not being visible.  
> We should have a table descriptor / family property, which would declare that the data
model does not use timestamps. Then we can populate this dimension with the seqId, so that
global ordering of edits are not effected by wall clock. 
> For example, META will use this. 
> Once we have something like this, we can think of making it default for new tables, so
that the unknowing user will not shoot herself in the foot. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message