You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2016/07/14 18:22:20 UTC

[jira] [Resolved] (UIMA-4920) fix a quirk in cas copier used for copy view then for individual FS copy

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

Marshall Schor resolved UIMA-4920.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.8.2SDK)

This is a very minor change, and not being fixed for the 2.8.x branch.  It is fixed in the 3.0.0SDKexp branch

> fix a quirk in cas copier used for copy view then for individual FS copy
> ------------------------------------------------------------------------
>
>                 Key: UIMA-4920
>                 URL: https://issues.apache.org/jira/browse/UIMA-4920
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>    Affects Versions: 2.8.1SDK
>            Reporter: Marshall Schor
>            Priority: Minor
>             Fix For: 3.0.0SDKexp
>
>
> If you use the cas copier to copy a view to another view, and reuse the same instance of the cas copier to copy fss, it remembers the view you were copying to, and sets the copied fs's to be in that view.  Although it isn't indexing, a subsequent fs_instance.addToIndexes will (if not a subtype of AnnotationBase) add the fs_instance to that last view, rather than the view the cas copier was initially specified with. 



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