You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ShardOperationFailureException implementations alread provide structured
exception support but it's not yet exposed on the interface. This change
allows nice rendering of structured REST exceptions also if searches fail on
only a subset of the shards etc.
Closeselastic#11017
ShardOperationFailureException implementations alread provide structured
exception support but it's not yet exposed on the interface. This change
allows nice rendering of structured REST exceptions also if searches fail on
only a subset of the shards etc.
Closeselastic#11017
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
May 18, 2015
ShardOperationFailureException implementations alread provide structured
exception support but it's not yet exposed on the interface. This change
allows nice rendering of structured REST exceptions also if searches fail on
only a subset of the shards etc.
Closeselastic#11017
Rendered as a structured exception:
However, if one shard succeeds, then exceptions are no longer structured:
Renders as:
Similarly, errors in bulk APIs are not structured:
Returns:
Curiously,
_msearch
doesn't return the reason if all shards failed:Returns:
The text was updated successfully, but these errors were encountered: