You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 23, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 23, 2021. It is now read-only.
Hey Lonnie - yea we're under-documented, for sure.
There's no REST interfaces, nor any HTTP servers generally to speak of here ... the best examples I can point you to are in the unit tests, but even those require some digging to understand.
Besides that, graphd operates a pretty simple protocol, it's line-oriented and you can use telnet to talk to it, or you can start it interactively with -y.
Also, will this current version of graphd horizontally scale with multiple instances as that would be really exciting to see.
Graphd sadly doesn't scale horizontally with respect to the graph - for example, i can't put different sections of the graph on different machines and serve queries consistently (this is an open problem!), but graphd does have a well-defined replication protocol and works in a master/replica pattern. This is a setup that allows you to run N replica graphd's, each containing a full copy of the graph data, and a single master (there are other setups, but this is the common one).
If you can choose what to write documentation about, I would like to read something about
Prerequisites
what graphd had been built to solve/optimize,
Operating Systems where graphd is known to run, recommended hardware features/configuration.
Usage
the process of inserting items (graphd -y vs. gld),
quitting graphd -y and the resulting state of the server (I would like to have a kind of REPL that I can quit and reenter),
best practices of mass data insertion,
best practices of data layout (type vs. typeguid, cost of primitives with names, values, strings in type [apparently the latter adds 2 additional primitives per line]).
Onboarding/Community
possibly a mailing list,
small downloadable example graphs,
the relation to other graph databases, e.g. Cayley.
Big thanks for sharing this repository! I don't mind sharing my experience with it, too, yet I miss a preferred platform.
These are great topics - I can cover some of them, others I'm going to have to either re-learn or go find an expert (I'm not the original author of any of this code, i'm just the steward).
If you could help me out with one more thing - could you order that list?
@teeler Hi, thanks for bringing this repo online.
I am a huge fan of freebase before it was shutdown. Glad to see the database which powers freebase now opensourced.
Since you are already writing an in-depth tutorial, could you illustrate how to load the freebase data?
e.g., load a small portion of freebase into graphd, and run some MQL queries.
Activity
teeler commentedon Sep 20, 2018
Hey Lonnie - yea we're under-documented, for sure.
There's no REST interfaces, nor any HTTP servers generally to speak of here ... the best examples I can point you to are in the unit tests, but even those require some digging to understand.
Just to get you over the hump did you look at https://github.com/google/graphd/blob/master/doc/graphd.8.md and https://github.com/google/graphd/blob/master/doc/graphd.conf.5.md?
Besides that, graphd operates a pretty simple protocol, it's line-oriented and you can use telnet to talk to it, or you can start it interactively with
-y.If you'd like to ask questions, feel free to chat: https://join.slack.com/t/mw-graphd/shared_invite/enQtNDMxNjU1OTcxMzQ3LTE1YmFmZWY1MjY2MmFkZDEwYTZhNzc1MGU5ZmY2ODc2OGFjYmU5ODU2MGI0ODAwOWRkNzdmZDc4ZmJiM2JmZmM
But i'll try writing a more in-depth tutorial in the meantime....
teeler commentedon Oct 31, 2018
There's a C client in the code (https://github.com/google/graphd/blob/master/libgraphdb/graphdb.h), and @pierogmorski is currently hacking away at a Go client (https://github.com/google/graphd/tree/master/go/graphd).
I also added a file that details the protocol (https://github.com/google/graphd/blob/master/doc/gr-protocol.txt, tl;dr its text based, newline-delimited)
Graphd sadly doesn't scale horizontally with respect to the graph - for example, i can't put different sections of the graph on different machines and serve queries consistently (this is an open problem!), but graphd does have a well-defined replication protocol and works in a master/replica pattern. This is a setup that allows you to run N replica graphd's, each containing a full copy of the graph data, and a single master (there are other setups, but this is the common one).
There's another doc that lightly describes other replica setup and status (https://github.com/google/graphd/blob/master/doc/gr-replication.txt).
laeuter commentedon Nov 24, 2018
If you can choose what to write documentation about, I would like to read something about
Prerequisites
Usage
Onboarding/Community
Big thanks for sharing this repository! I don't mind sharing my experience with it, too, yet I miss a preferred platform.
teeler commentedon Nov 27, 2018
These are great topics - I can cover some of them, others I'm going to have to either re-learn or go find an expert (I'm not the original author of any of this code, i'm just the steward).
If you could help me out with one more thing - could you order that list?
qiuwei commentedon Dec 13, 2018
@teeler Hi, thanks for bringing this repo online.
I am a huge fan of freebase before it was shutdown. Glad to see the database which powers freebase now opensourced.
Since you are already writing an in-depth tutorial, could you illustrate how to load the freebase data?
e.g., load a small portion of freebase into graphd, and run some MQL queries.
That would be super helpful.