[
https://issues.apache.org/jira/browse/TIKA-3352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321071#comment-17321071
]
Hudson commented on TIKA-3352:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-branch1x-jdk8 #115 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/115/])
TIKA-3352: Add json output for /tika endpoint in tika-server (tallison:
[https://github.com/apache/tika/commit/2006dc566c28f2655a8b7e625c49d6d1591e3d48])
* (add) tika-server/src/test/resources/mock/hello_world.xml
* (edit)
tika-server/src/main/java/org/apache/tika/server/resource/TikaResource.java
* (add)
tika-server/src/test/java/org/apache/tika/server/TikaResourceNoStackTest.java
* (edit)
tika-server/src/main/java/org/apache/tika/server/resource/RecursiveMetadataResource.java
* (edit) CHANGES.txt
* (edit)
tika-server/src/test/java/org/apache/tika/server/RecursiveMetadataResourceTest.java
* (add)
tika-server/src/test/java/org/apache/tika/server/TikaResourceMetadataFilterTest.java
* (edit) tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
* (add) tika-server/src/test/resources/mock/hello_world_long.xml
* (edit) tika-server/src/test/java/org/apache/tika/server/CXFTestBase.java
* (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java
* (edit) tika-server/src/test/java/org/apache/tika/server/StackTraceTest.java
* (add) tika-server/src/test/resources/configs/metadata-filter-include.xml
> Add a handler for json output from the /tika endpoint
> -----------------------------------------------------
>
> Key: TIKA-3352
> URL: https://issues.apache.org/jira/browse/TIKA-3352
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Fix For: 1.27
>
>
> I've been focusing mostly on the {{/rmeta}} endpoint. However, for many
> users who aren't enthusiasts of the wild and crazy things that can happen
> with embedded files (e.g., the rest of the world), it would be useful to have
> some of the advantages of the /rmeta endpoint without the complexity.
> This would allow text + metadata in the response (for those who don't want to
> parse the xhtml). It would include "late metadata", that is metadata that is
> only added after the content extraction has begun, which does not appear in
> our usual xhtml output. This would enable storing the stacktrace (if the
> -s/--stackTrace commandline option is selected) in a field (as is done in
> /rmeta) so that users would get what they could from a failed parse and be
> able to align parse exceptions with the detected mime type.
> Unlike /rmeta, this proposal would not include stacktraces from embedded
> files.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
