4 ms·
Ouch. A directed graph in a columnar store like HBase? I guess there are worse approaches, but I would like to see a justification for this other than "we hav
by evgen 17y ago
Ouch. A directed graph in a columnar store like HBase? I guess there are worse approaches, but I would like to see a justification for this other than "we have this hammer called Hadoop..."
- blasdel 17y agoGot any better solutions? I don't. At least it ain't trying to do it relationally! Tuplestores are one of the only data stores I can think of that doesn't actively fight you when trying to query EAV data or traverse Directed Graphs.
- epochwolf 17y agoIf it's a directed graph, why not use a graph database?
- blasdel 17y agoTuplestores are one of the most common backend formats for storing graphs — you only need triples, or quads if you want timestamps. Everything's stored as (Entity, Attribute, Value) in the same table, with all of the Es and As being references, and with the Vs as references when the tuple is a graph edge but as atoms when it's a graph node. Pretty much every existing RDF database is a tuplestore underneath, or abuses a relational database as a crappy tuplestore that won't get you fired for installing it.