You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (Jira)" <de...@uima.apache.org> on 2020/04/10 16:49:00 UTC
[jira] [Updated] (UIMA-6204) createReaderDescription does not
discover type priorities
[ https://issues.apache.org/jira/browse/UIMA-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho updated UIMA-6204:
---------------------------------------------
Fix Version/s: 3.1.0uimaFIT
> createReaderDescription does not discover type priorities
> ---------------------------------------------------------
>
> Key: UIMA-6204
> URL: https://issues.apache.org/jira/browse/UIMA-6204
> Project: UIMA
> Issue Type: Bug
> Components: uimaFIT
> Affects Versions: 2.4.0uimaFIT
> Reporter: Richard Eckart de Castilho
> Assignee: Richard Eckart de Castilho
> Priority: Major
> Fix For: 2.5.0uimaFIT, 3.1.0uimaFIT
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> createReaderDescription does not discover type priorities. This may cause the JCas to be incompletely initialised (i.e. without type priorities), e.g. when only such a reader is used in a JCasIterable. A workaround is to add a No-op analysis engine to the JCasIterable:
> {code}
> JCasIterable pipeline = SimplePipeline.iteratePipeline(readerDescription, createEngineDescription(NoOpAnnotator.class));
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)