[
https://issues.apache.org/jira/browse/TIKA-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335762#comment-17335762
]
Hudson commented on TIKA-3376:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #214 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/214/])
TIKA-3376 -- improve write limit reached handling in new /tika json output
(tallison:
[https://github.com/apache/tika/commit/9ac7e759b2007f541375ee2dedc736de5a555ccb])
* (edit)
tika-core/src/main/java/org/apache/tika/parser/RecursiveParserWrapper.java
* (edit)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/TikaResourceTest.java
* (edit)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/TikaResourceNoStackTest.java
* (edit)
tika-core/src/main/java/org/apache/tika/exception/WriteLimitReachedException.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/TikaResource.java
> Improve handling of write limit reached in new /tika json endpoint
> ------------------------------------------------------------------
>
> Key: TIKA-3376
> URL: https://issues.apache.org/jira/browse/TIKA-3376
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> If the server is not started with the -s option (show stacktrace), the new
> json endpoint for /tika should return 200 with a writelimitreached=true
> metadata value but no stacktrace.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
