User Story #1112 (new)
Opened 14 years ago
Last modified 14 years ago
Indexing might should be in-line
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | critical | Milestone: | Unscheduled |
| Component: | General | Keywords: | n.a. |
| Cc: | cxallan, jrswedlow | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Indexing currently happens in a background thread. Implementing that has been a fairly complicated task (#951, #1070, #1102, ...) and can cause memory issues (#1059).
It was designed background for two reasons:
# To speed up the individual update methods
# Because of previous limitations in the search library
If the second could be overcome, it might make sense to make indexing inline, slowing down each user a little on saves (higher latency) but working around many of the other issues we've had.
Change History (1)
comment:1 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Planning on revamping search in 4.1