REST Resources Remove/Delete not working
Calling remove/delete on the resources post does not seem to
have an effect. I called it yesterday on a particular resource and
it still appears as I browse the space and query for terms.
Comments are currently closed for this discussion. You can start a new one.
Support Staff 2 Posted by Chet Patel on 10 Mar, 2010 06:09 PM
so the resource ref is still there? What about the observation counts? thanks
3 Posted by Kyle Nakamoto on 10 Mar, 2010 06:14 PM
Yes, as far as I can tell the resource is still there. If I search for the terms, the entity still appears as a result. Also, an entity created from the record still appears in as I browse down through the REST interface.
As for observation counts, I didn't check before what they were, so I wouldn't be sure they changed. Also, how should I query for said observation counts?
Support Staff 4 Posted by Chet Patel on 10 Mar, 2010 06:19 PM
If you are ingesting a single resource, and then removing it, then there should not be any attributes for the empty connections call. Unless there are multiple resources with the same attributes modeled as memories, then the counts are going to be decremented.
5 Posted by Kyle Nakamoto on 10 Mar, 2010 08:12 PM
Okay. I set up a new space with one record. The counts are changing. The entity still sort of appears when browsing through REST memories interface.
This is a new space. I don't think I'm seeing this behavior from an existing space.
Support Staff 6 Posted by Chet Patel on 10 Mar, 2010 08:53 PM
Yes the entities are probably still there as rows and columns in the matrix but with no counts in them. This is by design. So that when another ingest comes with for that matrix it does not always re-create those rows and columns. If you are not seeing counts getting decrements in your main space then we have a problem.
7 Posted by Kyle Nakamoto on 11 Mar, 2010 07:35 PM
After our teleconference, we determined that the rest api did not add the source category to the resource ref. This resulted in a different resource to try to be deleted. There is an error that says the resource has been accepted which should be changed to indicate that there was a problem generating the resourceref or that the resourceref does not exist. The documentation for the REST resources interface should be modified to include the "source" name value.
Support Staff 8 Posted by Chet Patel on 12 Mar, 2010 04:54 PM
source is now included in the code and documented on the online docs.
Chet Patel closed this discussion on 12 Mar, 2010 04:54 PM.
Kyle Nakamoto re-opened this discussion on 12 Mar, 2010 05:01 PM
9 Posted by Kyle Nakamoto on 12 Mar, 2010 05:01 PM
Does this apply to the version (8.0.0-1784) we are running?
Support Staff 10 Posted by Chet Patel on 12 Mar, 2010 05:41 PM
yes, you have the source field in that version of the software..so your remove resource should work if you include the source tag in the POST body of the resource. I think when the datapump was originally used to ingest the resource, the source field was used with the ingest. Then in the REST api, the resource was being removed without the source field.
11 Posted by Jared Peterson on 15 Mar, 2010 03:37 PM
I'm going to close this down... Kyle, if you're not satisfied that we past this then simply reopen.
Jared Peterson closed this discussion on 15 Mar, 2010 03:37 PM.