You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Peter Klügl (JIRA)" <de...@uima.apache.org> on 2018/11/30 12:49:00 UTC

[jira] [Assigned] (UIMA-5910) Set annotation feature with allowedValues

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

Peter Klügl reassigned UIMA-5910:
---------------------------------

    Assignee: Peter Klügl

> Set annotation feature with allowedValues
> -----------------------------------------
>
>                 Key: UIMA-5910
>                 URL: https://issues.apache.org/jira/browse/UIMA-5910
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Ruta
>    Affects Versions: 2.6.2ruta
>            Reporter: Georg Bonczek
>            Assignee: Peter Klügl
>            Priority: Minor
>             Fix For: 2.6.2ruta
>
>         Attachments: allowedvalues.patch
>
>
> If an annotation type has a feature which range is a subtype of string ([https://uima.apache.org/d/uimaj-3.0.0/references.html#ugr.ref.xml.component_descriptor.type_system.string_subtypes|https://uima.apache.org/d/uimaj-3.0.0/references.html#ugr.ref.xml.component_descriptor.type_system.string_subtypes),] ) the usual feature assignments in e.g. CREATE calls do not work. They are not set due to the RutaStream::assignFeatureValue method not having an appropriate case for these range types.
> In the JCas cover classes however, the features can be directly set with strings.
> If not setting the feature value is not intended Ruta behavior, I attached a patch that might fix that issue. On my end, this works with all feature assignment methods.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)