uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marshall Schor <...@schor.com>
Subject Re: [jira] Commented: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
Date Tue, 28 Jul 2009 15:07:47 GMT
+1 -Marshall

Thilo Goetz (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/UIMA-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735944#action_12735944
> Thilo Goetz commented on UIMA-1257:
> -----------------------------------
> +1, sounds good.
> If I remember right, the changing type priorities are due to the fact that part of the
order is determined by iterating over the keys of a HashMap.  Since the HashMap implementation
changes now and then, this iterations sequence may depend on the JVM.
>> 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. 

View raw message