[
https://issues.apache.org/jira/browse/TIKA-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17394281#comment-17394281
]
Hudson commented on TIKA-3514:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #303 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/303/])
TIKA-3514 -- add parse success with exception (tallison:
[https://github.com/apache/tika/commit/d9b7b63e08405fdea40a83444aa96064ba1c6b9e])
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesClient.java
* (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
* (edit) tika-core/src/main/java/org/apache/tika/pipes/PipesServer.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesResource.java
> PipesResult should have a parse_success with parse exception option
> -------------------------------------------------------------------
>
> Key: TIKA-3514
> URL: https://issues.apache.org/jira/browse/TIKA-3514
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Trivial
> Fix For: 2.0.1
>
>
> If there's a catchable parse exception, the pipes server isn't transmitting
> that info back to the pipes client. The pipes client should return a
> pipesresult with status parse success w exception. The enduser shouldn't
> have to be responsible for digging into the metadata to figure out if there
> was a container exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
