Have you checked janusgraph source code , it used also hbase as a storage
backend:
http://janusgraph.org/
It combines it with elasticsearch for indexing. Maybe you can inspire from the
architecture there.
Generally, hbase it depends a lot on how the data is written to regions, the
order of data
Restarting this thread since it is relevant to us. We are thinking of using
HBase/Cassandra to store graph data and then load the data from here into
Flink/Gelly. One of the issues we are concerned about is the read
performance. So far we tried our tests with data residing on HDFS and that
worked f
Thank you for sharing!
On 28 July 2017 at 05:01, Robert Yokota wrote:
> Also Google Cloud Bigtable has such a page at https://cloud.google.com/
> bigtable/docs/integrations
>
> On Thu, Jul 27, 2017 at 6:57 PM, Robert Yokota wrote:
>
>>
>> One thing I really appreciate about HBase is its flexibi
Also Google Cloud Bigtable has such a page at
https://cloud.google.com/bigtable/docs/integrations
On Thu, Jul 27, 2017 at 6:57 PM, Robert Yokota wrote:
>
> One thing I really appreciate about HBase is its flexibility. It doesn't
> enforce a schema, but also doesn't prevent you from building a s
One thing I really appreciate about HBase is its flexibility. It doesn't
enforce a schema, but also doesn't prevent you from building a schema layer
on top. It is very customizable, allowing you to push arbitrary code to
the server in the form of filters and coprocessors.
Not having such higher-
Interesting blog.
>From your experience, is there anything on hbase side which you see room
for improvement ?
Which hbase release are you using ?
Cheers
On Thu, Jul 27, 2017 at 3:11 PM, Robert Yokota wrote:
> In case anyone is interested, I wrote a blog on how to analyze graphs
> stored in HB
