tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Burch (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-841) User supplied parsers should be preferred
Date Mon, 16 Jan 2012 12:22:39 GMT

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

Nick Burch commented on TIKA-841:

I would propose to fix this by adding logic similar to that in DefaultDetector to DefaultParser.
This would apply only to the ServiceLoader constructor, and would ensure that user parsers
go last in the list. The (MediaTypeRegistry, List<Parser>) constructor will allow people
to control their own ordering if they want
> User supplied parsers should be preferred
> -----------------------------------------
>                 Key: TIKA-841
>                 URL: https://issues.apache.org/jira/browse/TIKA-841
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: 1.0
>            Reporter: Nick Burch
> Currently, user supplied Detectors are preferred over built in ones, via logic in DefaultDetector.
This allows users to easily add their own detectors which are used in preference, as well
as making it easy to override the built in ones.
> However, there is no such logic for Parsers. Instead, the last parser in the DefaultParser
/ CompositeParser list for a given mimetype will be used (the map only holds one entry, so
last in wins). This makes it hard for users to override the parser for a type that the builtin
parsers support, as it isn't predictable where in the list parsers will go

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message