-
Suggestion
-
Resolution: Fixed
-
11
-
Problem Definition
Insight currently allows technically infinite (read that as "a lot") number of objects to be bulk deleted. Basically, whatever the number of objects returned in the IQL search falls within the scope of the delete operation.
Depending on the type of deletion (all objects in an object type, some objects based on IQL etc.) this operation includes very heavy sequential operations on the DB viz., Delete the attribute values, delete the attributes, delete the objects AND update all referenced objects to the deleting objects. Since there's no way of knowing all the references, currently insight does a scan of ALL OBJECTS and then updates the attributes of the existing objects referencing the deleting objects.
This way of handling bulk deletion causes:
- The UI progress "busy" animation stops even when the deletion is progressing in the background
- Indeterministic impression of results (sometimes 150 objects will be deleted all at once, sometimes it will still show 10 objects left since the background task is still ongoing and index is not yet updated)
- Database locking exception (viz., OptimisticLockException since user might think that the delete operation missed out on few objects and run a second pass)
Suggested Solution
- May be a "Progress bar" or something similar to let the user know there's "work in progress"
- May be, put a configurable limit the number of objects to be deleted by the object count settings on the UI with a max value of 1000 max objects (default) which can be further adjusted based on scenario, capacity etc.
Workaround
Detailed workaround is published in this KB: How to bulk delete Insight objects efficiently
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-7306] Improve Insight Bulk Delete operation
Hello, an improvement of the Insight bulk delete operation is really needed. I think that a progress bar in UI can really help, it is the one that both customers and partners require and it could be similar to the one available for Jira issue bulk delete.
On the other hand, it might help us partners at least to know in which file the activities related to the bulk delete request and its execution are logged.
I agree that the bulk delete mechanism should be improved from the objecttype tree view, but i think there shouldn't be a general limit of 1000 objects at a time.
Imagine if you have to delete 20k objects, you do not want to start the delete task 20 times. (Deleting would take ~12 Hours with Automation workaround via Rest API)
Hello - this says "Closed", but there doesn't seem to be any details of how it was fixed.
It says fixed in 5.7.0...