You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nick Burch (JIRA)" <ji...@apache.org> on 2015/06/08 16:13:00 UTC
[jira] [Created] (TIKA-1653) Tika config xml shouldn't read nested
parser definitions as top level
Nick Burch created TIKA-1653:
--------------------------------
Summary: Tika config xml shouldn't read nested parser definitions as top level
Key: TIKA-1653
URL: https://issues.apache.org/jira/browse/TIKA-1653
Project: Tika
Issue Type: Bug
Components: config
Affects Versions: 1.9
Reporter: Nick Burch
Spotted while looking at TIKA-1642, if you have some Tika config xml like:
{code}
<properties>
<parsers>
<parser class="org.apache.tika.parser.ctakes.CTAKESParser">
<parser class="org.apache.tika.parser.DefaultParser"/>
</parser>
</parsers>
</properties>
{code}
Then because of the way that TikaConfig is fetching the elements, it will process the DefaultParser once as a child of CTakes, then a second time at the top level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)