The current approach swallows to much information, because ES communications
most of the error via getDetailedMessage and not via getMessage. Therefore I
propose to report errors via the getDetailedMessage, at least in case of a
ElasticsearchException
The current approach swallows to much information, because ES communications most of the error via getDetailedMessage and not via getMessage. Therefore I propose to report errors via the getDetailedMessage, at least in case of a ElasticsearchException