uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Lally (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Reopened: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
Date Mon, 05 Jan 2009 21:25:44 GMT

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

Adam Lally reopened UIMA-1257:

Sorting the type definitions causes a change in the default type priorities.  This in turn
may break applications that are relying on the default type priorities.  Even though this
practice is not recommended, we should fix this to maintain compatibility.  What's needed
is to have the default type priorities based on the unsorted type definitions, but the assignment
of type codes to types based on sorted definitions.  

> Type System Merging Should Produce Consistent Ordering of Types
> ---------------------------------------------------------------
>                 Key: UIMA-1257
>                 URL: https://issues.apache.org/jira/browse/UIMA-1257
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2
>            Reporter: Adam Lally
>            Assignee: Adam Lally
>            Priority: Minor
>             Fix For: 2.3
> Currently when type systems are merged across annotators, the ordering of the types produced
by the merge method is not defined, and varies according to the ordering in which the individual
type system descriptors are passed to the merge method.  The ordering depends on the order
in which individual AEs are initialized, which is also not defined, and may even vary according
to JVM version.
> One reason to improve this is that UIMA-AS has a feature to allow binary serialization,
but it requires that type systems be identical on both sides of the connection, and it is
difficult to ensure this if ordering cannot be relied on. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message