tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Krugler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (TIKA-569) More fault-tolerant loading of parsers and detectors
Date Thu, 09 Dec 2010 18:24:02 GMT

    [ https://issues.apache.org/jira/browse/TIKA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969842#action_12969842
] 

Ken Krugler commented on TIKA-569:
----------------------------------

I'd run into this again recently, which made it clear the current architecture isn't resilient
to Tika code changes or parser changes.

The issue, IIRC, is that the new AutoDetectParser(parser... parsers) constructor now fails
because it calls something that eventually calls TikaConfig.getDefaultConfig(), which tries
to load all parsers on the classpath via DefaultParser.loadParsers().

I've got a pending fix for this particular issue, but it doesn't solve the fundamental problem.

And as Tika continues to add new parsers, with new 3rd party jar dependencies, the need to
run with a subset of parsers will only increase.


> More fault-tolerant loading of parsers and detectors
> ----------------------------------------------------
>
>                 Key: TIKA-569
>                 URL: https://issues.apache.org/jira/browse/TIKA-569
>             Project: Tika
>          Issue Type: Improvement
>          Components: config
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>
> Currently Tika will fail to start even if a single configured parser or detector can
not be loaded. Such cases occur often when required parser libraries or other dependencies
are not available, and it would be good if Tika could degrade more gracefully in such situations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message