Public | Automated Build

Last pushed: 4 months ago
Short Description
special-reports-rw-neo4j automated build
Full Description

DECOMISSIONED
See Concepts RW Neo4j instead

Special Reports Reader/Writer for Neo4j (special-reports-rw-neo4j)


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

Installation

For the first time:

go get github.com/Financial-Times/special-reports-rw-neo4j

or update:

go get -u github.com/Financial-Times/special-reports-rw-neo4j

Running

export|set PORT=8080
export|set NEO_URL={neo4jUrl}
export|set BATCH_SIZE=50
export|set GRAPHITE_TCP_ADDRESS=graphite.ft.com:2003
export|set GRAPHITE_PREFIX=coco.{env}.services.special-reports-rw-neo4j.{instanceNumber}
export|set LOG_METRICS=true
$GOPATH/bin/special-reports-rw-neo4j

With Docker:

docker build -t coco/special-reports-rw-neo4j .

docker run -ti --env NEO_URL=<base url> coco/special-reports-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.

NB: the default batchSize is much higher than the throughput the instance data ingester currently can cope with.

Endpoints

/special-reports/{uuid}

PUT

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 special report: unlike with GraphDB there is no check on whether the special report 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.

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

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

GET

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/special-reports/bba39990-c78d-3629-ae83-808c333c6dbc

DELETE

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

Admin endpoints

Healthchecks: http://localhost:8080/__health

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

Docker Pull Command
Owner
coco

Comments (0)