[
https://issues.apache.org/jira/browse/UIMA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339600#comment-16339600
]
Marshall Schor commented on UIMA-5662:
--------------------------------------
A close consideration of backwards compatibility shows that when users select
the v2-id-mode, the v3 implementation for XCAS and Compressed Binary form 6
differ from v2. For backwards compatibility, the implementation will change to
only serialize the reachables, just like v2 does.
> 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 prevent GC
> of unreachable FSs.
> # Based on a mode, set by -Duima.default_v2_id_references, and also
> controllable per CAS instance, support the use of id's in the same way V2
> did, with better support for more serialization/deserializations.
> Feature Structures when created are added to the internal
> id-to-FeatureStructure map, enabling the LowLevelCAS apis to work.
> # IDs are assigned so that mimic what they would be in V2
> # Serialization is altered to include unreachable Feature Structures for
> those serialization forms where this is the v2 worked. Forms like Xmi, XCAS,
> and compressed binary serialization form 6 only serialized reachable featrue
> structures in v2, and for backwards compatibility, this is continued.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
