IN-CORE Web Services is a component of IN-CORE. IN-CORE uses a service oriented architecture with a REST API for communicating with the different services.
Some datasets won't be able to be fetched or deleted through services, but they exist in mongodb. Even though the quota shows you still have a lot of room, the service still blocks you from creating new hazards because of you hit the quota limits.
Here are the datasets with problems:
654e39408df88731b20e3ae2
You can see them in mongodb, but can't GET/DELETE them
db.getCollection("EarthquakeDataset").find({"creator":"username"})
GET https://incore.ncsa.illinois.edu/hazard/api/earthquakes/654e39408df88731b20e3ae2DELETE https://incore.ncsa.illinois.edu/hazard/api/earthquakes/654e39408df88731b20e3ae2
Update
When we try create/get/delete an earthquake manually, everything works. But somehow requests through locust failed to add the hazard datasets to space correctly, that's the reason those hazard datasets can't be fetched/deleted through services.
what's done:
a script to add the hazard ids to the space correctly and delete them through service (in dev_script)
in locust, check the hazard is created before deleting it to allow the data service to add the hazards to space correctly before deleting them.
Issue
Some datasets won't be able to be fetched or deleted through services, but they exist in mongodb. Even though the quota shows you still have a lot of room, the service still blocks you from creating new hazards because of you hit the quota limits.
Here are the datasets with problems: 654e39408df88731b20e3ae2
You can see them in mongodb, but can't GET/DELETE them
db.getCollection("EarthquakeDataset").find({"creator":"username"})
GET https://incore.ncsa.illinois.edu/hazard/api/earthquakes/654e39408df88731b20e3ae2
DELETE https://incore.ncsa.illinois.edu/hazard/api/earthquakes/654e39408df88731b20e3ae2
Update
When we try create/get/delete an earthquake manually, everything works. But somehow requests through locust failed to add the hazard datasets to space correctly, that's the reason those hazard datasets can't be fetched/deleted through services.
what's done: