User Story #7019 (closed)
Opened 8 years ago
Closed 7 years ago
Importer client server interaction
| Reported by: | jburel | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4 |
| Component: | General | Keywords: | n.a. |
| Cc: | jamoore | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | 0.0d | Estimated Remaining Time: | n.a. |
Description
Similar to delete, change, group, scripting,
we should add check points so we can cancel any on-going import.
This can become an issue with large images.
Change History (5)
comment:1 Changed 8 years ago by jmoore
comment:2 Changed 8 years ago by jburel
I will go through the list of events sent, I think we tried with the ones we have/handle but it did not work correctly.
Currently I am finishing the importer as standalone so we only have one piece of code to maintain that will make the process easier. We could then be able to clean some of the code moved under the blitz section too.
comment:3 Changed 8 years ago by jburel
cancel the "looking for candidates" phase will be a good start
comment:4 Changed 8 years ago by agilo
- Status changed from new to accepted
Updated status, related task in progress
comment:5 Changed 7 years ago by jburel
- Resolution set to fixed
- Status changed from accepted to closed
see #8183
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Jean-Marie, where specifically do you want to cancel the import? The events give a lot of flexibility on stopping the process. Probably the biggest thing that's missing is having the server "rollback" all the changes (i.e. automatic delete).