[
https://issues.apache.org/jira/browse/TIKA-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978831#comment-16978831
]
Hudson commented on TIKA-2993:
------------------------------
SUCCESS: Integrated in Jenkins build tika-branch-1x #277 (See
[https://builds.apache.org/job/tika-branch-1x/277/])
TIKA-2993 -- tika-server's /rmeta endpoint shouldn't throw an exception
(tallison:
[https://github.com/apache/tika/commit/afab2a92f91ada54602b028d30979e048bdfbda2])
* (edit)
tika-server/src/main/java/org/apache/tika/server/resource/RecursiveMetadataResource.java
* (edit)
tika-server/src/test/java/org/apache/tika/server/RecursiveMetadataResourceTest.java
* (edit) tika-server/src/test/java/org/apache/tika/server/StackTraceOffTest.java
* (edit) tika-server/src/test/java/org/apache/tika/server/StackTraceTest.java
> tika-server's /rmeta endpoint shouldn't throw an exception for a parse
> exception
> --------------------------------------------------------------------------------
>
> Key: TIKA-2993
> URL: https://issues.apache.org/jira/browse/TIKA-2993
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Major
> Fix For: 1.23
>
>
> tika-server's /rmeta endpoint should catch exceptions and report them in the
> returned metadata list as happens with tika-app in batch mode.
> This includes parse exceptions, null-byte exceptions and encrypted document
> exceptions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
