anonlink-entity-service icon indicating copy to clipboard operation
anonlink-entity-service copied to clipboard

Privacy Preserving Record Linkage Service

Results 84 anonlink-entity-service issues
Sort by recently updated
recently updated
newest added

Warning message returned from flask: ``` 2019-08-26T06:50:42.576711Z [warning ] 2019-08-26T06:50:42.576711Z [warning ] handling the run status for state "error" is not implemented [entityservice.views.run.status] pid=bd94b382c9e7c461b841f66e133722cf45b04791a7c609f5 rid=3cbc915251091527d967c7c50d70e00da12f73f3b24a7ac0 [entityservice.views.run.status] pid=bd94b382c9e7c461b841f66e133722cf45b04791a7c609f5 rid=3cbc915251091527d967c7c50d70e00da12f73f3b24a7ac0 ```

This issue is to either modify the mapping output type to include the similarity score for the link. Or to add another output type that includes this score. Might mean...

effort3: hard (week)

Since #367 is closed (which should happen when #388 is merged), we have stopped using quay.io as repository for the entiy-service docker images, we are using dockerhub. But dockerhub doesn't...

backlog
devops

On a tagged commit the CI/CD system should push docker images with the correct version.

deployment
devops

See https://github.com/hadolint/hadolint

devops

Currently, to run the integration tests on kubernetes, we are creating a persistent volume, a job mounting the volume and saving the test results into it, and a final pod...

enhancement
integration tests
devops

When a run is created a task is added to the celery queue to *chunk* the similarity scoring work into multiple tasks - which are added to the same celery...

enhancement
feature request
devops

@wilko77 I noticed your [comment](https://github.com/data61/anonlink-entity-service/pull/379#issuecomment-502540424) that the testing deployment was down and had a look to see what was going on. The anonlink-entity-service `v1.11.0` has a traceback in the logs:...

Consider how we could scale using serverless functions in particular for the similarity scoring. https://knative.dev/docs/

enhancement
feature request

Following [this guidance](https://github.com/helm/charts/tree/master/stable/postgresql#use-of-global-variables), we now use a `global.postgresql` section so subcharts can access the postgres credentials without duplicating information. With redis we currently have to have the same password twice...

P4: nice to have
effort1: easy (hour)
deployment
devops