[
https://issues.apache.org/jira/browse/UIMA-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207279#comment-14207279
]
Marshall Schor commented on UIMA-4059:
--------------------------------------
The remove - modify - add sequence won't work if the user is inside an iterator
- currently causes concurrent modification exception. Even if the iterators
were "improved" to avoid this particular case, it then could happen that the
(modified) item would show up in the iteration at a later spot.
> add-to-indexes and checking for incorrect key modifications
> -----------------------------------------------------------
>
> Key: UIMA-4059
> URL: https://issues.apache.org/jira/browse/UIMA-4059
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 2.6.0SDK
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.7.0SDK
>
>
> Address the issue raised in Jiras UIMA-3399 and UIMA-4049, as follows: Add
> (under control of a Java jvm defined param - for backwards compatibility in
> unexpected edge cases, or if it is determined this has too big a
> performance/space cost) a set which tracks if a FS has been
> added/removed-to/from-the-indexes that has fast O(1) access. Change behavior
> of add-to-indexes when a FS has already been added to not add it again.
> Change behavior of feature structure value setting to throw an exception if
> the feature being set is used as a key in any index, and the FS has been
> added-to-the-indexes.
> This should address issues raised in both JIRAs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
