在 HBase 上使用 Janusgraph 时的一致性
consistency when using Janusgraph on HBase
我在 Janusgraph 文档中指出：
This page summarizes some of the aspects to consider when running JanusGraph on top of an eventually consistent storage backend like Apache Cassandra or Apache HBase.
但据我所知，HBase 在行级别上是强一致的。是不是和HBase涉及到多行时强一致不强有关，我不知道的HBase配置方式？
谢谢，
这是来自 janusgraph-user 邮件列表的答案：
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).
基本和你的回答一样，mbaxi。谢谢！
我在 Janusgraph 文档中指出：
This page summarizes some of the aspects to consider when running JanusGraph on top of an eventually consistent storage backend like Apache Cassandra or Apache HBase.
但据我所知，HBase 在行级别上是强一致的。是不是和HBase涉及到多行时强一致不强有关，我不知道的HBase配置方式？
谢谢，
这是来自 janusgraph-user 邮件列表的答案：
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).
基本和你的回答一样，mbaxi。谢谢！