Task #13074 (closed)
Bug: autoclose annotation scalability
Reported by: | mtbcarroll | Owned by: | jamoore |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-5.2.2 |
Component: | Import | Version: | OMERO-5.1.3 |
Keywords: | n.a. | Cc: | server@… |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | 0.0d |
Sprint: | n.a. |
Description
I used --auto_close in importing a directory of 1,000 images and ended up with the nth image having n openmicroscopy.org/omero/import/autoClose annotations on it, for 500,500 annotations in total.
Change History (5)
comment:1 Changed 8 years ago by jamoore
- Milestone changed from 5.x to OMERO-5.2.1
- Priority changed from major to critical
comment:2 Changed 8 years ago by jburel
- Milestone changed from OMERO-5.2.1 to OMERO-5.2.2
comment:3 Changed 8 years ago by jburel
- Milestone changed from OMERO-5.2.2 to OMERO-5.2.1
Milestone OMERO-5.2.2 deleted
comment:4 Changed 8 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
comment:5 Changed 8 years ago by jmoore <josh@…>
- Remaining Time set to 0
(In [d5935c334a23d27f9a9841b0522c1ed5906ccb86/ome.git] on branch develop) Prevent duplicate entries in annotation list (Fix #13074)
The List returned by getCustomAnnotationList was being set
in a fresh ImportSettings? instance by reference. Each fileset
and a single importCandidates run, however, shares the same
custom annotation list causing the list to incrementally grow
so that the Nth fileset had N auto-close annotations.
Using a newly created list solved the problem.
Milestone OMERO-5.2.1 deleted