[
https://issues.apache.org/jira/browse/TIKA-2979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978830#comment-16978830
]
Hudson commented on TIKA-2979:
------------------------------
SUCCESS: Integrated in Jenkins build tika-branch-1x #277 (See
[https://builds.apache.org/job/tika-branch-1x/277/])
TIKA-2979 -- tika-server shouldn't throw an exception for a file format
(tallison:
[https://github.com/apache/tika/commit/f216d84a9a6430fe370233a406054d157dc5fedb])
* (edit) tika-server/src/test/java/org/apache/tika/server/StackTraceTest.java
* (edit)
tika-server/src/test/java/org/apache/tika/server/UnpackerResourceTest.java
* (edit) CHANGES.txt
* (edit)
tika-server/src/main/java/org/apache/tika/server/resource/TikaResource.java
* (edit) tika-server/src/test/java/org/apache/tika/server/StackTraceOffTest.java
> tika-server shouldn't throw an exception for a non-supported format
> -------------------------------------------------------------------
>
> Key: TIKA-2979
> URL: https://issues.apache.org/jira/browse/TIKA-2979
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
> Fix For: 1.23
>
>
> tika-server throws an UnsupportedMediaTypeException if there is no parser for
> a given format. This prevents users from getting the mime type and any
> digests that were computed on the stream. Further this is different behavior
> than tika-app where we rely on the EmptyParser to do nothing.
> Is there a need for this exception?
> Would it be too great a change to turn off this behavior? If it would be,
> any recommendations for the commandline switch to turn it off?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
