[
https://issues.apache.org/jira/browse/UIMA-4059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-4059:
---------------------------------
Description:
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}}.
was:
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.
Affects Version/s: (was: 2.6.0SDK)
Summary: Checking for incorrect key modifications (was:
add-to-indexes and checking for incorrect key modifications)
Change this Jira to just address the additional optional checking for
modification of a key used in any index in any View. UIMA-3399 is the issue
for the change in behavior for multiple addToIndexes for the same identical FS
> 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)
