Re: is hbase backend eventually consistent
Jerry He <jerr...@...>
HBase is strong consistency (as compared to eventual consistency).
I agree the chapter is confusing. What it says is that because the backends lack multiple row transaction consistency (for both Cassandra and HBase, as compared to a ACID system), JanusGraph employs some home-made mechanisms to support transaction consistency. The mechanism takes into consideration and covers the 'eventual consistency' issue as well (for Cassandra).
Hope this helps.
Jerry
On Fri, Sep 28, 2018 at 4:59 AM, <jele...@...> wrote:
I have red here : https://docs.janusgraph.org/--latest/eventual-consistency. html that hbase is "eventually consistent". However, as far as I know Hbase is strongly consistent, at the row level. I don't understand ... has it something to do with the fact that hbase is not consistent when multiple rows are involded, or a way of configuring hbase that I do not know about ?Thanks !
You received this message because you are subscribed to the Google Groups "JanusGraph users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-users+unsubscribe@googlegroups.com.
To post to this group, send email to janusgraph-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-users/ 9e1cdbf3-2d0f-40b6-af09- c8cd962ccc7b%40googlegroups. com.
For more options, visit https://groups.google.com/d/optout.