Rename triple entities were relevant
This commit is contained in:
parent
ddf8849e60
commit
443a091b72
62 changed files with 664 additions and 664 deletions
|
|
@ -23,7 +23,7 @@ All command line flags take precedence over the configuration file.
|
|||
|
||||
* `mem`: An in-memory store, based on an initial N-Quads file. Loses all changes when the process exits.
|
||||
* `leveldb`: A persistent on-disk store backed by [LevelDB](http://code.google.com/p/leveldb/).
|
||||
* `bolt`: Stores the graph data on-disk in a [Bolt](http://github.com/boltdb/bolt) file. Uses more disk space and memory than LevelDB for smaller stores, but is often faster to write to and comparable for large ones, with faster average query times.
|
||||
* `bolt`: Stores the graph data on-disk in a [Bolt](http://github.com/boltdb/bolt) file. Uses more disk space and memory than LevelDB for smaller stores, but is often faster to write to and comparable for large ones, with faster average query times.
|
||||
* `mongo`: Stores the graph data and indices in a [MongoDB](http://mongodb.org) instance. Slower, as it incurs network traffic, but multiple Cayley instances can disappear and reconnect at will, across a potentially horizontally-scaled store.
|
||||
|
||||
#### **`db_path`**
|
||||
|
|
@ -33,7 +33,7 @@ All command line flags take precedence over the configuration file.
|
|||
|
||||
Where does the database actually live? Dependent on the type of database. For each datastore:
|
||||
|
||||
* `mem`: Path to a triple file to automatically load.
|
||||
* `mem`: Path to a quad file to automatically load.
|
||||
* `leveldb`: Directory to hold the LevelDB database files.
|
||||
* `bolt`: Path to the persistent single Bolt database file.
|
||||
* `mongo`: "hostname:port" of the desired MongoDB server.
|
||||
|
|
@ -64,7 +64,7 @@ All command line flags take precedence over the configuration file.
|
|||
* Type: Integer
|
||||
* Default: 10000
|
||||
|
||||
The number of triples to buffer from a loaded file before writing a block of triples to the database. Larger numbers are good for larger loads.
|
||||
The number of quads to buffer from a loaded file before writing a block of quads to the database. Larger numbers are good for larger loads.
|
||||
|
||||
#### **`db_options`**
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ The size in MiB of the LevelDB write cache. Increasing this number allows for mo
|
|||
* Type: Integer
|
||||
* Default: 2
|
||||
|
||||
The size in MiB of the LevelDB block cache. Increasing this number uses more memory to maintain a bigger cache of triple blocks for better performance.
|
||||
The size in MiB of the LevelDB block cache. Increasing this number uses more memory to maintain a bigger cache of quad blocks for better performance.
|
||||
|
||||
### Bolt
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ Arguments:
|
|||
* a string: A single tag to add the predicate used to the output set.
|
||||
* a list of strings: Multiple tags to use as keys to save the predicate used to the output set.
|
||||
|
||||
Out is the work-a-day way to get between nodes, in the forward direction. Starting with the nodes in `path` on the subject, follow the triples with predicates defined by `predicatePath` to their objects.
|
||||
Out is the work-a-day way to get between nodes, in the forward direction. Starting with the nodes in `path` on the subject, follow the quads with predicates defined by `predicatePath` to their objects.
|
||||
|
||||
Example:
|
||||
```javascript
|
||||
|
|
@ -117,7 +117,7 @@ Arguments:
|
|||
* a string: A single tag to add the predicate used to the output set.
|
||||
* a list of strings: Multiple tags to use as keys to save the predicate used to the output set.
|
||||
|
||||
Same as Out, but in the other direction. Starting with the nodes in `path` on the object, follow the triples with predicates defined by `predicatePath` to their subjects.
|
||||
Same as Out, but in the other direction. Starting with the nodes in `path` on the object, follow the quads with predicates defined by `predicatePath` to their subjects.
|
||||
|
||||
Example:
|
||||
```javascript
|
||||
|
|
@ -235,7 +235,7 @@ Arguments:
|
|||
* `predicate`: A string for a predicate node.
|
||||
* `tag`: A string for a tag key to store the object node.
|
||||
|
||||
From the current node as the subject, save the object of all triples with `predicate` into `tag`, without traversal.
|
||||
From the current node as the subject, save the object of all quads with `predicate` into `tag`, without traversal.
|
||||
|
||||
Example:
|
||||
```javascript
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ Responses come in the form
|
|||
|
||||
#### `/api/v1/write`
|
||||
|
||||
POST Body: JSON triples
|
||||
POST Body: JSON quads
|
||||
|
||||
```json
|
||||
[{
|
||||
|
|
@ -94,7 +94,7 @@ POST Body: JSON triples
|
|||
"predicate": "Predicate Node",
|
||||
"object": "Object node",
|
||||
"label": "Label node" // Optional
|
||||
}] // More than one triple allowed.
|
||||
}] // More than one quad allowed.
|
||||
```
|
||||
|
||||
Response: JSON response message
|
||||
|
|
@ -114,7 +114,7 @@ curl http://localhost:64210/api/v1/write/file/nquad -F NQuadFile=@30k.n3
|
|||
|
||||
#### `/api/v1/delete`
|
||||
|
||||
POST Body: JSON triples
|
||||
POST Body: JSON quads
|
||||
|
||||
```json
|
||||
[{
|
||||
|
|
@ -122,7 +122,7 @@ POST Body: JSON triples
|
|||
"predicate": "Predicate Node",
|
||||
"object": "Object node",
|
||||
"label": "Label node" // Optional
|
||||
}] // More than one triple allowed.
|
||||
}] // More than one quad allowed.
|
||||
```
|
||||
|
||||
Response: JSON response message.
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Predicates always assume a forward direction. That is,
|
|||
}]
|
||||
```
|
||||
|
||||
will only match if the triple
|
||||
will only match if the quad
|
||||
```
|
||||
A some_predicate B .
|
||||
```
|
||||
|
|
@ -54,7 +54,7 @@ exists. In order to reverse the directions, "!predicates" are used. So that:
|
|||
}]
|
||||
```
|
||||
|
||||
will only match if the triple
|
||||
will only match if the quad
|
||||
```
|
||||
B some_predicate A .
|
||||
```
|
||||
|
|
|
|||
|
|
@ -29,13 +29,13 @@ You can repeat the `--db` and `--dbpath` flags from here forward instead of the
|
|||
First we load the data.
|
||||
|
||||
```bash
|
||||
./cayley load --config=cayley.cfg.overview --triples=30kmoviedata.nq.gz
|
||||
./cayley load --config=cayley.cfg.overview --quads=30kmoviedata.nq.gz
|
||||
```
|
||||
|
||||
And wait. It will load. If you'd like to watch it load, you can run
|
||||
|
||||
```bash
|
||||
./cayley load --config=cayley.cfg.overview --triples=30kmoviedata.nq.gz --alsologtostderr
|
||||
./cayley load --config=cayley.cfg.overview --quads=30kmoviedata.nq.gz --alsologtostderr
|
||||
```
|
||||
|
||||
And watch the log output go by.
|
||||
|
|
@ -82,7 +82,7 @@ Along the side are the various actions or views you can take. From the top, thes
|
|||
* Query (a request/response editor for the query language)
|
||||
* Query Shape (a visualization of the shape of the final query. Does not execute the query.)
|
||||
* Visualize (runs a query and, if tagged correctly, gives a sigmajs view of the results)
|
||||
* Write (an interface to write or remove individual triples or triple files)
|
||||
* Write (an interface to write or remove individual quads or quad files)
|
||||
|
||||
----
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue