[
https://issues.apache.org/jira/browse/UIMA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295148#comment-16295148
]
Marshall Schor commented on UIMA-5662:
--------------------------------------
Re: "choose between stable addresses and GC on a per-CAS-instance base even
when working with multiple CASes simultaneously in a single thread".
Both the bit-in-the-CAS and the thread-local approaches would support this
requirement. The bit-in-the-cas is obvious - set the bit in the cas for the
mode and then be careful to use that particular CAS in a way that's aligned
with that mode. Make sure the mode is proper if you "check out" a new cas from
a cas pool, etc.
The thread-local approach would take code that was doing some deserialization
and surround it with a (e.g.) try-with-resources, setting the proper mode.
This might be more visible in the code, and the try-with-resources would
document exact boundaries where this mode was to be in effect. I'm still
leaning slightly in favor of this 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)
