You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2021/10/13 16:35:00 UTC
[jira] [Commented] (TIKA-3573) Refactor new external parser to get
rid of the check
[ https://issues.apache.org/jira/browse/TIKA-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428332#comment-17428332 ]
Hudson commented on TIKA-3573:
------------------------------
FAILURE: Integrated in Jenkins build Tika ยป tika-main-jdk8 #340 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/340/])
TIKA-3573 -- remove check (tallison: [https://github.com/apache/tika/commit/415caf2c7fca793adef10187420226c87738773a])
* (edit) tika-core/src/main/java/org/apache/tika/parser/external2/ExternalParser.java
* (edit) tika-core/src/test/resources/org/apache/tika/config/TIKA-3557.xml
> Refactor new external parser to get rid of the check
> ----------------------------------------------------
>
> Key: TIKA-3573
> URL: https://issues.apache.org/jira/browse/TIKA-3573
> Project: Tika
> Issue Type: Wish
> Reporter: Tim Allison
> Priority: Trivial
> Fix For: 2.1.1
>
>
> In the recently added o.a.t.parser.external2.ExternalParser, I included a "check cmd" call. We don't need that because the point of this parser is that users need to specify the parser via tika-config.xml. The point in the previous ExternalParser was "run the external parser if the executable is available." In the newer parser, if the executable does not exist, users will get parse errors.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)