[
https://issues.apache.org/jira/browse/TIKA-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12834783#action_12834783
]
Jukka Zitting commented on TIKA-378:
------------------------------------
How about if we introduced a protected TikaConfig method like
handleParserLoadFailure(String parserClassName, Throwable throwable) that does
nothing by default but that you could override to add whatever logging or other
error handling?
The rationale for silently ignoring such errors is the fairly common scenario
where just a subset of the required parser libraries is in the classpath but
you still want to use the default Tika configuration without adjusting it to
match the available libraries.
> TikaConfig should notify users if it cannot initialize some parser
> ------------------------------------------------------------------
>
> Key: TIKA-378
> URL: https://issues.apache.org/jira/browse/TIKA-378
> Project: Tika
> Issue Type: Bug
> Components: config
> Affects Versions: 0.6
> Reporter: Sami Siren
>
> It would be nice if TikaConfig would somehow signal that it cannot load
> parser classes. Currently it just silently ignores all throwables.
> I would be ok with about any kind of signaling (even just wrapping and
> rethrowing the exception). If we wan't to maintain back compat in
> functionality we could indroduce a new config option into the configuration
> file or a method in TikaConfig class that would enable rethrowing exceptions
> on parser initializations.
> What do others think?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
