Date
1 - 3 of 3
Regarding DB
|
Kalpa 1977
Thanks for the clarifications. Kalpa On Sun, Jul 31, 2022 at 3:46 PM <hadoopmarc@...> wrote:
|
|
|
|
1. Sure, see: https://github.com/JanusGraph/janusgraph/blob/master/LICENSE.txt
2. JanusGraph backends are not columnar in the usual meaning of the word, but rather assume a BigTable like KeyColumnValue store, see https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-core/src/main/java/org/janusgraph/diskstorage/keycolumnvalue/KeyColumnValueStore.java This provides better horizontal scalability than technologies like solr/elacticsearch. A KeyColumnValue store client can see from the partitioned key which backend node to address, while solr/elastic involves a server-side routing step to direct a query to the right shard when requesting a specific document by id. This might be different for your inhouse store, though, so check whether it can implement the interface above efficiently. You may also want to check https://li-boxuan.medium.com/janusgraph-deep-dive-data-layout-in-janusgraph-cd33c045a495 whether your store supports this data layout. |
|
|
|
Kalpa 1977
Hi All,
My company has a inhouse db like elasticsearch but only index based search, no columnar. I see that janusgraph mostly has columnar db as the primary data storage. 1. can we plugin our own db, is it allowed? 2. why only columnar as the primary db, any reasons. index based lucene also can support like getting all the indexed documents. any reason why columnar as the primary backend? thanks, Kalpa |
|
|