[UIMA-4535] Flatten indexes need to be invalidated when switching to JCas

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.8.0SDK
• Fix Version/s: 2.8.1SDK
• Component/s: Core Java Framework
• Assignee: Marshall Schor
• Reporter: Marshall Schor
• Created: 24/Jul/15 19:35
• Updated: 27/Jul/15 21:51
• Resolved: 27/Jul/15 21:51

Description

uima 2.8.0 introduced automatically-generated "flattened-indexes", created after measurements of use indicate it would be beneficial to replace iteration over a type with (lots of) subtypes, with a flattened version of that index. These flattened versions hold the Java cover class instantiation of the instances.

If these are created before JCas is used, then the cover classes are the non-JCas ones, e.g. FeatureStructureImpl or AnnotationImpl. After the JCas is used, the generators are switched to use the JCas ones.

A problem occurs in this case: JCas is not used, a flattened index is created, JCas is activated, and then an iteration is done over the flattened index. This iteration will return the non-JCas versions of the cover classes, potentially causing class cast exceptions.

The fix, I think, is to invalidate any flattened indexes that might exist in all views, the first time JCas use is started.

Issue Links

• is duplicated by: UIMA-4542 edge cases need Flattened index invalidation