Bug 50605

GemStone/S 64 Bit

3.7.1, 3.7, 3.6.8, 3.6.7, 3.6.6, 3.6.5, 3.6.4, 3.6.3, 3.6.2, 3.6.1, 3.6, 3.5.8, 3.5.7, 3.5.6, 3.5.5, 3.5.4, 3.5.3, 3.5.2, 3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.x, 3.3, 3.2.16, 3.2.15, 3.2.x, 3.2

Indexing feature optionalPathTerms not working correctly

The indexing feature optionalPathTerms allows you to create an index on a collection in which some objects along the path do not have an instance variable present in the index path. The index is created on the objects in which the instance variable is present without erroring on the object in which is it absent.

However, if an object along the path that does not have the instance variable is replaced by an object that does have it, the optionalPathTerm index is not updated to reflect the presence of the objects that are now reachable.

This failure is not detected by index audit.

Workaround

For collections with optionalPathTerm indexes, if objects on the path change, you should rebuild the index.


                

Last updated: 7/19/23