[
https://issues.apache.org/jira/browse/UIMA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295319#comment-16295319
]
Richard Eckart de Castilho commented on UIMA-5662:
--------------------------------------------------
Re "... as objects in the CAS, customized by users for what they want (e.g.
weak references, etc.)" - in general, I think this is a great idea. But as far
as I have understood the proposals so far for realizing this, the management of
these sets/maps would be entirely up to client code. Now, if it were possible
to somehow hook into to the lifecycle of annotations in the CAS e.g. to
register a callback which automatically records an id<->FS mapping whenever a
annotation is instantiated or added to an index, remove such a mapping when it
is removed from an index (or when it is garbage collected), it might be more
convenient. Yet still, I believe that UIMA itself should provide a built-in
default mechanism for id<->FS mapping and that the custom mappings should just
be something that users could do in addition to the built-in approach.
> uv3 support CAS deserialization subsequent low level access
> -----------------------------------------------------------
>
> Key: UIMA-5662
> URL: https://issues.apache.org/jira/browse/UIMA-5662
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 3.0.0SDK-beta
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDK
>
>
> Some users depend 1) constant v2-ids for FSs preserved in deserialization and
> serialization, and 2) low level cas API access to these.
> V3 normally doesn't maintain tables linking ids to FSs, as these (unless weak
> refs are used) prevent GC of unreachable FSs.
> Based on a mode, set by -Duima.deserialize_perserve_ids, and also
> controllable by new config option per deserialize call, alter the
> deserialization for those deserializers which know about v2 ids, to put these
> into the map used for low-level CAS access, using the actual v2 ids, and
> change the v3 next available id for future new FSs to be 1 beyond the end.
> The -Duima.deserialize-preserve_ids global setting is needed to handle the
> use case of some annotators using low-level APIs, when part of a pipeline is
> "remoted".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
