uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marshall Schor (JIRA)" <...@uima.apache.org>
Subject [jira] [Resolved] (UIMA-5662) uv3 support CAS deserialization subsequent low level access
Date Thu, 25 Jan 2018 18:52:00 GMT

     [ https://issues.apache.org/jira/browse/UIMA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marshall Schor resolved UIMA-5662.
    Resolution: Fixed

> 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
>  # 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
>  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

View raw message