[jira] [Issue Comment Deleted] (UIMA-4059) Checking for incorrect key modifications

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

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

Marshall Schor updated UIMA-4059:
---------------------------------
    Comment: was deleted

(was: 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.  )

> 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
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>            Priority: Minor
>             Fix For: 2.7.0SDK
>
>
> Address the issue raised in Jira UIMA-4049, as follows: Add an optional check that checks, for every set of a Feature value, whether or not that Feature is used as a key in any Sort or Set index, and if so, if the Feature Structure is currently in any index in any View; if so, an exception is thrown.  
> This additional check is normally disabled, but can be enabled by specifying the JVM property {{-Duima.check_invalid_fs_updates}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)