Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1390 (closed)

Opened 15 years ago

Closed 9 years ago

Search : bridges miss updates.

Reported by: jamoore Owned by: jamoore
Priority: critical Milestone: 5.1.1
Component: Search Version: 3.0-M1
Keywords: n.a. Cc: carlos@…, jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jmoore)

With moderately sophisticated SearchBridges which walk the graph adding various objects to the backlog for re-indexing, there is a possibility that some changes will go missed.

Even the default bridge which indexes annotations along with the annotated objects misses updates:

  1. Image created with annotation
  2. Image is indexed with annotation
  3. Annotation is modified
  4. Only annotation index is updated

Currently, for performance reasons all annotated objects are not searched for when an annotation is modified, but it will need to be. A workaround is to also modify the annotated object when saving the annotation:

 // pseudo-code
 image.setVersion( image.getVersion() + 1 )

See also #1386

Change History (7)

comment:1 Changed 15 years ago by jmoore

  • Description modified (diff)
  • Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2

comment:2 Changed 14 years ago by jmoore

  • Milestone changed from OMERO-Beta4.2 to Unscheduled

comment:3 Changed 14 years ago by jmoore

  • Description modified (diff)
  • Priority changed from major to critical
  • Summary changed from Complicated bridges can miss updates due to backlog to Search : bridges miss updates.
  • Type changed from User Story to defect

comment:4 Changed 14 years ago by jmoore

  • Type changed from Bug to Task

comment:5 Changed 14 years ago by jmoore

(In [7323]) Adding new sequences and triggers to 4.2 DB. (See #1390, #2508)

comment:6 Changed 14 years ago by jburel

  • Cc jburel added

comment:7 Changed 9 years ago by jamoore

  • Milestone changed from Unscheduled to 5.1.1
  • Resolution set to fixed
  • Status changed from new to closed

This was all fixed via triggers some time ago.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.72002 sec.)

We're Hiring!