tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Allison (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-2977) Tika should throw an exception if a custom parser specified in tika-config.xml can't be loaded
Date Tue, 29 Oct 2019 16:25:00 GMT

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

Tim Allison resolved TIKA-2977.
-------------------------------
    Resolution: Not A Problem

User error. I was missing the {{loadErrorHandler}} in my config.

{noformat}
<service-loader initializableProblemHandler="throw" loadErrorHandler="throw"/>
{noformat}

> Tika should throw an exception if a custom parser specified in tika-config.xml can't
be loaded
> ----------------------------------------------------------------------------------------------
>
>                 Key: TIKA-2977
>                 URL: https://issues.apache.org/jira/browse/TIKA-2977
>             Project: Tika
>          Issue Type: Improvement
>            Reporter: Tim Allison
>            Assignee: Tim Allison
>            Priority: Major
>
> If you start tika-server and specify a custom parser class in tika-config _but_ you don't
then include that jar on the classpath, tika-server silently fails.  
> I initially thought that we should make sure that it respects the service loader problem
handler (e.g. <service-loader initializableProblemHandler="throw"/>), but this isn't
service loading.  If a user specifies a parser that can't be loaded, we should throw an exception.
 WDYT?
> This also affects tika-app in regular and batch mode.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message