Brian Thorne
Brian Thorne
Ensure that tutorials link to api spec, linkage schema and relevant more detailed docs
I suspect that if we had a special queue for processing worker requests to delete a project we might avoid a lot of unnecessary work while testing. It might be...
As each PII field may have different types of errors (e.g. missing data, transcription error, entirely changed data...) we need to document any built in assumptions. - Matching common names:...
The tests are currently written to work entirely through the REST api - this is good for e2e style tests as we don't have to have special access to the...
In an internal logging discussion we decided that each project should have the ability to log to postgresql.
See https://github.com/n1analytics/entity-service/pull/219 > init-db-schema.sql was failing because it was trying to create tables that already existed. > I suggest adding a test to make sure that init-db-schema.sql can be executed...
In [/backend/entityservice/serialization.py#L166](https://github.com/n1analytics/entity-service/blob/c1cd83a9ee2a0f73a5c4bc029a2c499eb757b8d7/backend/entityservice/serialization.py#L166) we stream the results to avoid having to load the whole dataset into memory at once. However as in #184, connexion is very strict about json validation. It...
At the moment results are json and must fit in memory to keep connexion happy. We could instead serve static files directly using nginx. Perhaps the [X-Accel](https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/) headers could be...