[
https://issues.apache.org/jira/browse/UIMA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor closed UIMA-1840.
--------------------------------
Fix Version/s: 2.3.1
Resolution: Fixed
ResultSpecification_impl has new static method that takes 2 ResultSpec_impls
and intersects them, following language subsumption rules. The Javadocs for
containsType and containsFeature are clarified to represent what they do in all
the specific cases of language subsumption. The PrimitiveAnalysisEngine_impl
is modified to cache the resultSpec corresponding to its output capabilities,
everytime the type system changes. The call to do the intersection is changed
to use the new method in the ResutlSpecification_impl. The old method,
computeAnalysisComponentResultSpec, is commented out. I hope no users made use
of this (we'll soon see ...). I made a new set of test cases for this
(ResultSpecTest), and moved the resultSpec test from the
AnalysisEngine_implTest, and modified it to work (it needs the type system
specified, in order to compute the intersection for these tests).
uimaj core tests all run OK, including new ones.
> Result Specification behavior incorrect for aggregates
> ------------------------------------------------------
>
> Key: UIMA-1840
> URL: https://issues.apache.org/jira/browse/UIMA-1840
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Eddie Epstein
> Assignee: Marshall Schor
> Fix For: 2.3.1
>
>
> For a scenario using default result specifications, if an annotator with
> language "x-unspecified" is included in an aggregate with a different
> language, say "en", any containsType method calls from the annotator will
> return false.
> This behavior is incorrect given that the annotator has declared that it will
> work with any language.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
