we are using the Attachment plugin to extract plain text from diverse file types like PDFs. All in all, this works fine, no problems here. However, if, for some reason normally not connected to extraction as such, we get an exception as response, say an UnavailableShardsException, this response is huge and generates unnecessary network traffic, because Elasticsearch includes the complete request with its base64-encoded file content in that response!
Is it possible to configure Elasticsearch such that it leaves the request or at least the "source" part containing the base64'ed content out of the response? Or is it possible to tell it to do so per request?
Thanks and best regards