uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie Epstein <eaepst...@gmail.com>
Subject Re: [jira] [Created] (UIMA-3399) More consistent handling of multiple add-to-index behavior for same Feature Structure
Date Mon, 04 Nov 2013 14:08:28 GMT
Consider a scenario where an annotator needs to remove
an FS from the index repository. The only way to do this currently
is to repeatedly remove FS from index until it is no longer there.
Is that consistent or well documented?

Do we know yet how much overhead Marshall is proposing?


On Sat, Nov 2, 2013 at 7:25 AM, Thilo Goetz <twgoetz@gmx.de> wrote:

> On 02.11.2013 11:33, Richard Eckart de Castilho wrote:
>> On 02.11.2013, at 11:17, Thilo Goetz <twgoetz@gmx.de> wrote:
>>  On 01.11.2013 22:13, Marshall Schor wrote:
>> <snip>
>>  I don't know of any cases where the same FS was *intentionally* added to
>>>> the
>>>> indexes multiple times; so I'm hoping (!) that changing this behavior
>>>> won't
>>>> break existing things.
>>> The why go to all this trouble to fix a non-existent issue?
>> The current behavior is inconsistent and apparently undesired. We could
>> nail
>> the  behavior down to a desired state before somebody starts relying on
>> it,
>> and runs into problems, e.g. when mixing remote and local operations, or
>> when
>> moving from local to remote. I'd consider being forced to maintain
>> inconsistencies
>> as another maintenance nightmare.
>> -- Richard
> The current behavior of the local case is consistent, documented and
> works as designed.  I have still not heard an argument that would
> convince me that adding the overhead Marshall is proposing to the
> local implementation is in any way more desirable or easier than
> to make the remote implementation consistent with the local one.
> --Thilo

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message