uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] Closed: (UIMA-1840) Result Specification behavior incorrect for aggregates
Date Tue, 03 Aug 2010 14:47:16 GMT

     [ https://issues.apache.org/jira/browse/UIMA-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marshall Schor closed UIMA-1840.

    Resolution: Fixed

Implement a valid equals method for resultSpecs - old method only tested 2 of the fields (was
defaulting from a superclass). This equals method is used in the test case to compare actual
and expected result specs.  Implement a hashcode that throws unsupported operation, since
computing a true hashcode is very expensive and isn't done.
One test broke in AnalysisEngine_implTest - where it compared the ResultSpec sent in (which
had a type with language x-unspecified), with the resultSpec sent to the last primitive (which
had an output capability of "en" for that type) - which made the result spec there != to the
one sent in (it was "narrowed" to "en").

Fixed the method that added a spec to the new resultSpec in intersection to work, given that
the bitsets for languages are not necessarily compatible.

Added a test case to the ResultSpecTest and verified it failed before the fix, and worked

All tests ran OK.

> 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.

View raw message