User Story #955 (closed)
Opened 16 years ago
Closed 16 years ago
Add re-indexing callback from within `FieldBridge` implementations
Reported by: | jamoore | Owned by: | jamoore |
---|---|---|---|
Priority: | major | Milestone: | 3.0-Beta3 |
Component: | Search | Keywords: | search, callback, synchronization, stale |
Cc: | Story Points: | n.a. | |
Sprint: | n.a. | Importance: | n.a. |
Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
Each call to iUpdate.indexObject() or FieldBridge.set() involves a single object. The interface provides the Lucene Document which represents the object. There's no way to access Documents for related objects (like the Images within a Project). A callback should be added to allow such re-indexing.
See: SearchBridges and ticket:954
Change History (5)
comment:1 Changed 16 years ago by jmoore
comment:2 Changed 16 years ago by jmoore
Incomplete support in r2363
comment:3 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta3 to 3.0-Beta4
Is a fairly complex requirement, possibly requiring notifications itself. Pushing.
comment:4 Changed 16 years ago by jmoore
comment:5 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta4 to 3.0-Beta3
- Resolution set to fixed
- Status changed from new to closed
r2491 solves the issues of annotations. When an annotation link is indexed, the parent gets scheduled for indexing via the ReindexMessage. This still does not solve the blind side of a unidirectional relationship, but if versions don't nothing will.
One remaining weakness in with this solution will be that when indexing Annotations it will not be possible to navigate to the containing object and schedule them for re-indexing. This holds for all objects which are on the blind side of a unidirectional relationship.