We are also looking at increasing timestamp resolution in a backwards
compatible way (see https://issues.apache.org/jira/browse/HBASE-8927).
If we do introduce the concept of a "timestamp multiplier" per table, then
Bryan's suggestion could be an option without the regret. Clients could
learn the
Agree. You should not rely on timestamp uniqueness to resolve version
conflicts. Design your key appropriately and provide support for conflict
resolution on a client side. Guide is a good example.
On Jun 5, 2015 8:58 AM, "Bryan Beaudreault"
wrote:
> I wouldn't say it is recommended, but it is ce
I wouldn't say it is recommended, but it is certainly possible to override
the version timestamp at write time. You might be able to use this to
provide the uniqueness you need (i.e. instead of using epoch timestamp,
use one based more recently and add digits for uniqueness at the end).
We've do
Dia:
Have you tried command in the following form in hbase shell ?
hbase> t.get 'r1', {COLUMN => 'c1', TIMERANGE => [ts1, ts2], VERSIONS =>
4}
Cheers
On Fri, Jun 5, 2015 at 8:50 AM, Dia Kharrat wrote:
> Ted: Yes, I've already read the HBase documentation, but didn't find
> anything that dire
Ted: Yes, I've already read the HBase documentation, but didn't find
anything that directly answered my question. My question was simply whether
it's possible to get cells with the same timestamp with concurrent Puts to
the same cell.
Vlad: Thanks for the information. Yep, I've also noticed the be
>> Please read http://hbase.apache.org/book.html#_store
How does this answer original question?
-Vlad
On Thu, Jun 4, 2015 at 6:30 PM, Ted Yu wrote:
> Dia:
> Please read http://hbase.apache.org/book.html#_store
>
> Cheers
>
> On Thu, Jun 4, 2015 at 6:02 PM, Vladimir Rodionov
> wrote:
>
> > Yes
Dia:
Please read http://hbase.apache.org/book.html#_store
Cheers
On Thu, Jun 4, 2015 at 6:02 PM, Vladimir Rodionov
wrote:
> Yes, last write wins (with higher sequenceId). MemStore will resolve this
> conflict and only the last
> put will be added eventually, unless ... between these two puts Me
Yes, last write wins (with higher sequenceId). MemStore will resolve this
conflict and only the last
put will be added eventually, unless ... between these two puts MemStore's
snapshot is created.
I this case put #1 will be saved in a snapshot and eventually will make it
into a store file, but thi
I'm trying to confirm the behavior of HBase when there are concurrent
writes to the same cell that happen at the exact same millisecond and not
providing a timestamp value to the Put operations (i.e. relying on current
time of region server). Is it possible that such concurrent writes result
in a c
