[ https://issues.apache.org/jira/browse/TIKA-3376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17335747#comment-17335747 ]
Hudson commented on TIKA-3376: ------------------------------ SUCCESS: Integrated in Jenkins build Tika ยป tika-branch1x-jdk8 #122 (See [https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/122/]) TIKA-3376 improve handling of write limit reached in json output from /tika endpoint (tallison: [https://github.com/apache/tika/commit/32545d471b2ecdc57c64813c40cf834d55dc8f77]) * (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceNoStackTest.java * (edit) tika-server/src/main/java/org/apache/tika/server/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)