tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TIKA-660) Remove logging of duplicate parser definitions
Date Wed, 18 May 2011 16:03:47 GMT

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

Jukka Zitting resolved TIKA-660.

       Resolution: Fixed
    Fix Version/s: 1.0

In revision 1124309 I moved this functionality to an explicit findDuplicateParsers() method
that interested clients can use to find duplicate parser definitions.

> Remove logging of duplicate parser definitions
> ----------------------------------------------
>                 Key: TIKA-660
>                 URL: https://issues.apache.org/jira/browse/TIKA-660
>             Project: Tika
>          Issue Type: Improvement
>          Components: parser
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 1.0
> In TIKA-620 (revision 1085003) we added logging for cases where more than one parser
is defined for the same media type. This is good for catching issues like classpath conflicts,
but not for cases like in Jackrabbit where we use configuration [1] to explicitly override
the parsers of certain media types.
> Because of this issue and the general preference of no logging in tika-core I'd like
to remove this logging functionality. If it's needed in some use cases, we could instead create
a utility tool that goes through a list of parsers and finds all the duplicates. Deployments
that want to avoid duplicates could then use this tool to flag them.
> [1] http://svn.apache.org/repos/asf/jackrabbit/branches/2.2/jackrabbit-core/src/main/resources/org/apache/jackrabbit/core/query/lucene/tika-config.xml

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message