1. Messages
  2. HBase table definition and how flexible to change it?

Re: HBase table definition and how flexible to change it?

Demai <nid...@...>
 

Jerry,

thanks for the pointer. Since they are stored in different CFs, it is a bit similar as Neo4j.  I have the janusGraph up and running on my mac on top of HBase 1.2, thanks for the effort to make it supporting newer HBase version, will play with it as your suggested.

Demai


On Friday, February 10, 2017 at 10:33:39 AM UTC-8, Jerry He wrote:
The edges, vertices, properties and indexes are stored in a fixed table and a fixed set of column families within the table in HBase. i.e. edges are in one CF, properties are in another CF.
They are linked via the rowkey / ID.
It is probably not clearly documented anywhere. You may need to look into the org.janusgraph.diskstorage.hbase package.
Also you can start up JanusGraph with HBase, create the sample graph.  Then look at and scan the table to get a feeling.

Jerry
Join {janusgraph-dev@lists.lfaidata.foundation to automatically receive all group messages.