[
https://issues.apache.org/jira/browse/TIKA-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17282502#comment-17282502
]
Tim Allison edited comment on TIKA-3297 at 2/10/21, 3:16 PM:
-------------------------------------------------------------
We should prevent excluded parsers/detectors from being loaded at all...not
just excluded after initialization as we are currently doing.
This will save on resources and prevent confusion about whether the tika-config
file is being processed.
was (Author: [email protected]):
We should prevent excluded parsers/detectors from being loaded at all...not
just excluded after initialization.
> Simplify parser configuration in 2.x
> ------------------------------------
>
> Key: TIKA-3297
> URL: https://issues.apache.org/jira/browse/TIKA-3297
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
> Fix For: 2.0.0
>
>
> We currently have .properties files and tika-config.xml and runtime
> configuration. We should simplify to tika-config.xml.
> From a security perspective, I'm thinking we should also allow executable
> paths to be set only via tika-config.xml...not programmatically via a
> TesseractConfig.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
