[
https://issues.apache.org/jira/browse/TIKA-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382303#comment-17382303
]
Hudson commented on TIKA-3482:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #284 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/284/])
TIKA-3482 -- improve handling of fetch exceptions, add basic logging to
tika-app -a (tallison:
[https://github.com/apache/tika/commit/dd5f49fc5ac751a8aa67e29e4c4c6963ca8ea65e])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesResult.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/async/AsyncProcessor.java
* (add) tika-core/src/test/resources/test-documents/subdir/example.xml
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
* (edit)
tika-core/src/test/java/org/apache/tika/pipes/pipesiterator/FileSystemPipesIteratorTest.java
* (edit) tika-app/src/main/java/org/apache/tika/cli/TikaCLI.java
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
> Improve handling of FetchException in pipes processor
> -----------------------------------------------------
>
> Key: TIKA-3482
> URL: https://issues.apache.org/jira/browse/TIKA-3482
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> In the current implementation, if there's a fetch exception, that causes the
> forked process to restart. We should transmit that exception back to the
> forking process and not restart.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
