[
https://issues.apache.org/jira/browse/UIMA-6199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055388#comment-17055388
]
Marshall Schor commented on UIMA-6199:
--------------------------------------
Here's what's happening. In v3, unreachable FSs are normally not serialized.
In the cases that are failing, a Document Annotation is being made reachable
(either by setting ALWAYS_HOLD_ONTO_FSS, or by having an indexed FS (Refer)
which holds a reference to it.
When the Document Annotation is deserialized, the deserialized code
(erroneously in this case) assumes it is to be indexed, and automatically adds
it to the index. The deserialization code uses the
view.getDocumentAnnotation() method, which special cases the creation of this
by (a) insuring only one of them is created, and (b) adding it to the indexes
for this view if it was created.
This last bit of adding it to the indexes is what's going wrong. This
deserialization code is used by many deserialization methods, and has multiple
use cases, so it will take some time to figure out an appropriate fix for this.
> Unindexed document annotation added back to index during deserialization
> ------------------------------------------------------------------------
>
> Key: UIMA-6199
> URL: https://issues.apache.org/jira/browse/UIMA-6199
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Affects Versions: 3.1.1SDK
> Reporter: Richard Eckart de Castilho
> Priority: Major
> Fix For: 3.2.0SDK
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If a CAS contains a document annotation that was removed from the indexes, it
> may be added back to the indexes during deserialization if
> {{CASImpl.ALWAYS_HOLD_ONTO_FSS}} is {{true}}.
> There is also a second scenario triggering this issue that works without
> enabling {{CASImpl.ALWAYS_HOLD_ONTO_FSS}}. It involves creating an FS which
> references the document annotation before removing it from the indexes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
