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] [Updated] (UIMA-4677) UV3 Internal support for Feature Structure IDs
Date Fri, 02 Sep 2016 18:09:21 GMT

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

Richard Eckart de Castilho updated UIMA-4677:
---------------------------------------------
    Description: 
Feature Structures have IDs; these show up in externalized formats.  In v2, these were the
int heap address. In V3, -these are incrementing ints, starting at 1.- these are designed
to mimic v2, for backwards compatibility (and to support use-cases that rely on IDs as proxies
for actual references to FS objects).

Support is needed for PEARs and for low-level createFS methods to hold onto FSs to prevent
them from being garbage collected.  This is provided using a map from IDs to the FS.

  was:
Feature Structures have IDs; these show up in externalized formats.  In v2, these were the
int heap address. In V3, -these are incrementing ints, starting at 1.- these are designed
to mimic v2, for backwards compatibility.

Support is needed for PEARs and for low-level createFS methods to hold onto FSs to prevent
them from being garbage collected.  This is provided using a map from IDs to the FS.


> UV3 Internal support for Feature Structure IDs
> ----------------------------------------------
>
>                 Key: UIMA-4677
>                 URL: https://issues.apache.org/jira/browse/UIMA-4677
>             Project: UIMA
>          Issue Type: Sub-task
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 3.0.0SDKexp
>
>
> Feature Structures have IDs; these show up in externalized formats.  In v2, these were
the int heap address. In V3, -these are incrementing ints, starting at 1.- these are designed
to mimic v2, for backwards compatibility (and to support use-cases that rely on IDs as proxies
for actual references to FS objects).
> Support is needed for PEARs and for low-level createFS methods to hold onto FSs to prevent
them from being garbage collected.  This is provided using a map from IDs to the FS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message