tballison commented on PR #2962:
URL: https://github.com/apache/tika/pull/2962#issuecomment-5038806867
K, this one is more important. We should surface the source of the problem
when a payload is too big.
```
Recommendation this surfaces (I'd promote it above my #3/#4): give the limit
breach a distinct, honest status — a TASK_EXCEPTION-category value like
OUTPUT_TOO_LARGE / PAYLOAD_LIMIT_EXCEEDED — caught specifically in
PipesClient so that: the client gets a clear, actionable error with the size in
it, the server is not restarted, and tika-server surfaces the reason in
the response body. Right now the PR makes the ceiling tunable but leaves the
diagnosis when it trips as a mislabeled crash. Worth raising with the
author — arguably the change isn't complete without it.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
