[
https://issues.apache.org/jira/browse/TIKA-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14333266#comment-14333266
]
Tim Allison commented on TIKA-1558:
-----------------------------------
I agree with Nick that I'd prefer to migrate more and more control to a config
file than relying on SPI in the long term. As Nick observes on TIKA-1557,
there is a way to do this now with the config file, but more work remains
before we're ready to fully move to a config file.
[~thetaphi], from a Solr/DIH perspective, would Solr users prefer SPI or a
config file?
> Create a Parser Blacklist
> -------------------------
>
> Key: TIKA-1558
> URL: https://issues.apache.org/jira/browse/TIKA-1558
> Project: Tika
> Issue Type: New Feature
> Reporter: Tyler Palsulich
> Assignee: Tyler Palsulich
> Fix For: 1.8
>
>
> As talked about in TIKA-1555 and TIKA-1557, it would be nice to be able to
> disable Parsers without pulling their dependencies out. In some cases (e.g.
> disable all ExternalParsers), there may not be an easy way to exclude the
> dependencies via Maven.
> So, an initial design would be to include another file like
> {{META-INF/services/org.apache.tika.parser.Parser.blacklist}}. We create a
> new method {{ServiceLoader#loadServiceProviderBlacklist}}. Then, in
> {{ServiceLoader#loadServiceProviders}}, we remove all elements of the list
> that are assignable to an element in
> {{ServiceLoader#loadServiceProviderBlacklist}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
