-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Improvement][V1] Delete all entities for a given type #1645
Comments
Thank for the feedback. We acknowledgue this issue as part of our backlog (note the "backlog" label) and eventually we will deal with it. On the meanwhile, a workaround (easy to implement in integrated testing) is to cleanup the Orion DB entities collection before each test, e.g.;
|
(Semi offtopic: note that |
+1 to this feature. I would suggest adding to v2 API features |
It has been explicetly mentioned in the issue about NGSIv2 |
This issue is related with #1503, which is more general about updates using id pattern for entities. |
The following SOF question may need update after completing this issue: http://stackoverflow.com/questions/39732799/orion-context-broker-delete-several-entities-at-one-call/39776195#39776195 |
Definitely a +1 :) |
+1 |
The following SOF question has to be updated after completing this issue: https://stackoverflow.com/questions/47889912/fiware-orion-remove-all-entities-of-the-same-type |
The following script can be useful to delete all entities (of a given type and/or matching a given filter) while this issue gets implemented: https://github.com/telefonicaid/fiware-orion/blob/master/scripts/utils/delete_entities.py |
I was wondering about the status? Thanks. |
No news as far as I know. The issue is waiting a brave developer to take care of it :) |
In order to run automatic integration testing of an app using Orion CB, it would be useful to be able to delete all entities (for instance before installing fixtures), so the test can run in a deterministic environment.
In V1 it is not possible to delete multiple entities in a single operation
Fails with
The text was updated successfully, but these errors were encountered: