Task #2792 (closed)
Opened 14 years ago
Closed 14 years ago
Handle non-deleted delete logs if possible
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-Beta4.2.1 |
| Component: | Services | Version: | n.a. |
| Keywords: | n.a. | Cc: | |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | 0.0d |
| Sprint: | 2010-09-30 (17) |
Description (last modified by jmoore)
#2791 provides a simple solution to recording which objects get deleted, but there is a race condition. After the query which loads the ids to be deleted, it is possible that someone else removes the object, causing the delete to do nothing. In that case, multiple event logs for the delete may be created. One possible solution would be to add a UNIQUE to EventLog?. However, how exactly the UniqueConstraint should be handled is unclear.
Note: If delete logs are added inappropriately, then the objects will be removed from the search index.
Change History (6)
comment:1 Changed 14 years ago by jmoore
- Priority changed from minor to major
comment:2 Changed 14 years ago by jmoore
- Description modified (diff)
- Priority changed from major to critical
- Remaining Time changed from 0.5 to 1.5
comment:3 Changed 14 years ago by jmoore
comment:4 Changed 14 years ago by atarkowska
- Sprint set to 2010-09-09 (16)
comment:5 Changed 14 years ago by jburel
- Sprint changed from 2010-09-09 (16) to 2010-09-30 (17)
comment:6 Changed 14 years ago by jmoore
- Remaining Time changed from 1.5 to 0
- Resolution set to fixed
- Status changed from new to closed
The performance seems to be acceptable for 4.2.1. Closing.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
(In [8123]) Deleting by rows rather than by bulk; possible performance impact (See #2792)