As a REST endpoint /drop, which should delete the given dataset.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Hjfocs | T169044 Implement the Ingestion API | |||
| Resolved | Hjfocs | T170684 Implement the drop service |
Event Timeline
Comment Actions
As per https://wiki.blazegraph.com/wiki/index.php/REST_API#DELETE_with_Access_Path, the request below works fine:
curl --get -X DELETE 'http://localhost:9999/bigdata/sparql' --data-urlencode 'c=<${DATASET_URI}>'
where ${DATASET_URI} is the named graph URI (see T170685) of the dataset we want to drop.
Of course, exposing this is not safe at all.
Comment Actions
The service is already available via the /sparql endpoint.
See T170819 to limit this action to the user who has uploaded the dataset.
Comment Actions
Considering that the probability of someone deleting his dataset is relatively low we could hide this endpoint from the public (avoiding the security work needed to secure it) and provide an email to ask the removal of the dataset instead.