[
https://issues.apache.org/jira/browse/TIKA-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-1323.
-------------------------------
Resolution: Fixed
r1661193
Commandline option -includeStack will enable this behavior. I centralized and
made exception handling more uniform for parsing for /tika, /unpack and /rmeta.
/meta is still slightly different for backwards compatibility.
> Improve exception reporting in JAX-RS server
> --------------------------------------------
>
> Key: TIKA-1323
> URL: https://issues.apache.org/jira/browse/TIKA-1323
> Project: Tika
> Issue Type: Improvement
> Components: server
> Reporter: Tim Allison
> Priority: Minor
>
> I'd like to use tika-server for TIKA-1302. As part of that, I'd like to
> record exception stacktraces per document. I see two options: transmit the
> info back to the client (assuming a doc didn't bring the server down :) )
> along with the current error code or log the document id and stacktrace via
> the server. Given my current design thoughts, I'd prefer the first option.
> Any objections or recommendations?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
