Public | Automated Build

Last pushed: a year ago
Short Description
Automated build for the alphaville series R/W
Full Description

See Concepts RW Neo4j instead

AlphavilleSeries Reader/Writer for Neo4j (alphaville-series-rw-neo4j)

An API for reading/writing alphaville-series into Neo4j. Expects the alphaville-series json supplied to be in the format that comes out of the alphaville-series transformer.


For the first time:

go get

or update:

go get -u


export|set PORT=8080
export|set NEO_URL={neo4jUrl}
export|set BATCH_SIZE=50
export|set GRAPHITE_PREFIX=coco.{env}.services.alphaville-series-rw-neo4j.{instanceNumber}
export|set LOG_METRICS=true

With Docker:

docker build -t coco/alphaville-series-rw-neo4j .

docker run -ti --env NEO_URL=<base url> coco/alphaville-series-rw-neo4j

All arguments are optional, they default to a local Neo4j install on the default port (7474), application running on port 8080, batchSize of 1024, graphiteTCPAddress of "" (meaning metrics won't be written to Graphite), graphitePrefix of "" and logMetrics false.




"The only mandatory fields are the uuid, the prefLabel and the alternativeIdentifier uuids (because the uuid is also listed in the alternativeIdentifier uuids list)."

Every request results in an attempt to update that series: unlike with GraphDB there is no check on whether the series already exists and whether there are any changes between what's there and what's being written. We just do a MERGE which is Neo4j for create if not there, update if it is there.

A successful PUT results in 200.

We run queries in batches. If a batch fails, all failing requests will get a 500 server error response.

Invalid json body input, or uuids that don't match between the path and the body will result in a 400 bad request response.

curl -XPUT -H "X-Request-Id: 123" -H "Content-Type: application/json" localhost:8080/alphaville-series/bba39990-c78d-3629-ae83-808c333c6dbc --data '{"uuid":"bba39990-c78d-3629-ae83-808c333c6dbc","prefLabel":"Metals Markets", "type":"AlphavilleSeries", "alternativeIdentifiers":{"TME":["MTE3-U3ViamVjdHM="], "uuids": ["bba39990-c78d-3629-ae83-808c333c6dbc","6a2a0170-6afa-4bcc-b427-430268d2ac50"]}}'

The type field is not currently validated - instead, the AlphavilleSeries Writer writes type AlphavilleSeries and its parent types (Thing, Concept, Classification, AlphavilleSeries) as labels for the AlphavilleSeries.


The internal read should return what got written

If not found, you'll get a 404 response.

Empty fields are omitted from the response.
curl -H "X-Request-Id: 123" localhost:8080/alphaville-series/bba39990-c78d-3629-ae83-808c333c6dbc


Will return 204 if successful, 404 if not found
curl -XDELETE -H "X-Request-Id: 123" localhost:8080/alphaville-series/bba39990-c78d-3629-ae83-808c333c6dbc

Admin endpoints

Healthchecks: http://localhost:8080/__health

Ping: http://localhost:8080/ping or http://localhost:8080/__ping


When you test integration with concept-ingester outside clustered container environment, e.g. your local machine,
the workaround is to use localhost:{--port}/__alphaville-series-rw-neo4j/alphaville-series/
instead of localhost:8080/alphaville-series/.

This is because you are not likely to have Vulkan to resolve hosts ports and paths in your local environment.

Running in your local environment

alphaville-series-rw-neo4j --port=XXXX

Docker Pull Command