Re: [jira] Commented: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
+1 -Marshall Thilo Goetz (JIRA) wrote: [ https://issues.apache.org/jira/browse/UIMA-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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.
[jira] Commented: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
[ https://issues.apache.org/jira/browse/UIMA-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12735825#action_12735825 ] Adam Lally commented on UIMA-1257: -- I've rethought my last comment. I recently happened to accidentally discover that default type priorities can change even from something like changing from Java 5 to Java 6. So given that we already have unpredictable default type priorities, I don't feel so bad about introducing a different change that shakes them up. In fact, once this change is implemented, it will add more stability going forward. Any objection if I close this issue and leave the code in there that sorts types alphabetically prior to creating the CAS? 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.
[jira] Commented: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
[ https://issues.apache.org/jira/browse/UIMA-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12735896#action_12735896 ] Burn Lewis commented on UIMA-1257: -- +1 for sorting, and hence providing a consistent ordering when users forget to explicitly specify type priorities. Ensures portability with a low one-time cost. 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.
[jira] Commented: (UIMA-1257) Type System Merging Should Produce Consistent Ordering of Types
[ https://issues.apache.org/jira/browse/UIMA-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
