Task #10973 (new)
Opened 11 years ago
Last modified 8 years ago
OMERO.searcher features are stored in two places (server 500 error if not stored correctly) — at Version 1
| Reported by: | spli | Owned by: | spli |
|---|---|---|---|
| Priority: | minor | Milestone: | Unscheduled |
| Component: | Scripting | Version: | n.a. |
| Keywords: | searcher | Cc: | analysis@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by spli)
Image features are currently stored in two places:
- An omero.tables HDF5 table attached to that image (contains features for only that image).
- The ContentDB
The ContentDB is used for most operations, however the per-image HDF5 tables are used to check the available feature scales for candidate images. It would be better to store everything in one place.
This would avoid the situation where features have been stored in a table but the ContentDB update operation fails- in this situation if you attempt to run a search you will end up with a 500 error.
Change History (1)
comment:1 Changed 11 years ago by spli
- Description modified (diff)
- Summary changed from OMERO.searcher features are stored in two places to OMERO.searcher features are stored in two places (server 500 error if not stored correctly)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
