[
https://issues.apache.org/jira/browse/UIMA-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15477339#comment-15477339
]
Marshall Schor commented on UIMA-5102:
--------------------------------------
In the case where this happened, it was good there was an error thrown, because
the issue was caused by out-of-sync updating a type system, and then trying to
use it to read previously generated xmi files (which were scheduled to be
updated, but hadn't been yet).
So, there's value in this being an error, as well as otherwise. Although
outputting a message might help (but there's so much output these days into
logs that doesn't get read....)
> auto set missing AnnotationBase sofaRef feature
> -----------------------------------------------
>
> Key: UIMA-5102
> URL: https://issues.apache.org/jira/browse/UIMA-5102
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.9.0SDK
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDKexp, 2.9.1SDK
>
>
> This Jira describes a possible approach to automatically recovering from an
> error condition, which might be implemented.
> Sometimes, the sofa feature of a FS which is a subtype of AnnotationBase is
> missing (is null) when the FS is being added to the indexes of some
> particular CAS View. One way this can happen is during (lenient)
> deserialization of XMI or XCAS CASes, after some update has occurred to the
> type system, which changes a type from not being a subtype of AnnotationBase,
> to having that as a supertype.
> In this case (where the sofa reference is null), instead of throwing an
> exception, set the sofa reference to the likely proper value - the sofa that
> corresponds to the view it is being indexed in. If there is no sofa for that
> view (unlikely but possible), throw an exception.
> If this recovery is done, output a diminishing frequency log message about
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
