uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Eckart de Castilho (JIRA)" <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-5106) uv3 constant "id" for FSs (Proposed new Feature for uv3)
Date Fri, 18 Nov 2016 21:47:59 GMT

    [ https://issues.apache.org/jira/browse/UIMA-5106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677858#comment-15677858

Richard Eckart de Castilho commented on UIMA-5106:

In WebAnno, we're using the FS address for this - it remains stable as long as we use SerialFormat.SERIALIZED_TSI
or SerialFormat.SERIALIZED.

> uv3 constant "id" for FSs (Proposed new Feature for uv3)
> --------------------------------------------------------
>                 Key: UIMA-5106
>                 URL: https://issues.apache.org/jira/browse/UIMA-5106
>             Project: UIMA
>          Issue Type: New Feature
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>            Priority: Minor
> Add constant ID for FSs. This would be an incrementing, long value. It would be constant
through serialization/ deserialization cycles. There would be a lazily created map from longs
to FSs (via weak links) to allow direct access from the ID to the FS.  Lazy intent is to not
have a cost for this (space/time) other than the cost for 1 long / FS, if it is not used.
> We could make this feature optional, as well, to avoid the 8 bytes per FS overhead, but
in V3, I think that's not a good tradeoff (space savings vs complexity).  
> Issues: 
> * Current design allows parallelism of services, with returned results "stacked" into
receiving CAS; would need to change (some of) the IDs coming back.
> CAS would need to have the high-water-mark value as part of serializations.
> Backwards compatibility:
> * loading V2 CASs: generate new IDs upon loading.
> * serializing to V2: (for connecting to V2 services): drop the IDs.
> This is a proposed new V3 feature; comments appreciated.

This message was sent by Atlassian JIRA

View raw message