[
https://issues.apache.org/jira/browse/UIMA-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573016#action_12573016
]
Marshall Schor commented on UIMA-830:
-------------------------------------
Are there any implications from the standards work being done here?
As I recall, there was some thinking around the "coupling" between "views" and
"sofas", looking toward generalizations of this. Currently, we have a
one-to-one coupling between these. This change would seem to require that
one-to-one coupling, but I admit to not really doing any deep thinking on this.
Are there use cases that would help us think this through, better?
> add method cas.deleteView()
> ---------------------------
>
> Key: UIMA-830
> URL: https://issues.apache.org/jira/browse/UIMA-830
> Project: UIMA
> Issue Type: New Feature
> Reporter: Eddie Epstein
>
> All CAS content except for SofaFS can be "deleted" by removing any references
> to it. The data is not actually deleted, but data without references is left
> out of future XML serializations of the CAS.
> The proposal here is to allow deletion of SofaFS, by deleting the view
> containing it. The actions would be to clear out the view's index repository
> and un-index the SofaFS. These are a few lines of code.
> However, if the SofaFS or any annotations in that view are referenced by FS
> in other views, these FS would still be serialized out. An additional check
> could be put into serialization to ignore un-indexed SofaFS and any
> annotations pointing to such a SofaFS. Here again, a few lines of code, but
> with some additional overhead to serialization of annotations.
> Comments?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
