[
https://issues.apache.org/jira/browse/TIKA-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650478#comment-14650478
]
Nick Burch commented on TIKA-1702:
----------------------------------
After a fair bit of refactoring of the logic in Tika Config, common code is now
used for Parsers, Detectors and Translators. For Detectors, that means you can
now create a CompositeDetector from config with custom ordering, and exclude
Detectors from DefaultDetector. A config examples of this is available in the
unit tests. That's all there as of r1693747.
As we now have common logic for creating Parsers, Detectors and Translators
from the Tika Config XML, the process of expanding this support with
options/parameters from the ongoing "Configuring parsers and translators"
discussion should be much easier now
> Tika config xml support for detectors
> -------------------------------------
>
> Key: TIKA-1702
> URL: https://issues.apache.org/jira/browse/TIKA-1702
> Project: Tika
> Issue Type: Improvement
> Components: config
> Affects Versions: 1.9
> Reporter: Nick Burch
> Priority: Minor
>
> Currently, you can use the Tika Config XML to have very fine-grained control
> over what parsers to use, in what order, for what mimetypes etc.
> While the same decoration needs won't apply/be appropriate for detectors, the
> ordering part / composites part / excluding part does. We should therefore
> add similar support for detectors for those areas
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
