Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nest 1.0 does not expose failure reason for failed shards #930

Closed
bittusarkar opened this issue Sep 7, 2014 · 1 comment
Closed

Nest 1.0 does not expose failure reason for failed shards #930

bittusarkar opened this issue Sep 7, 2014 · 1 comment

Comments

@bittusarkar
Copy link

For ES query fired at an index having say 5 shards, if correct results are returned from 4 shards and an exception thrown from one shard, the ES JSON response for _shards section may look something like below:

"_shards": {
      "total": 5,
      "successful": 4,
      "failed": 1,
      "failures": [
         {
            "index": "<indexname>",
            "shard": 4,
            "status": 500,
            "reason": "<error message>"
         }
      ]
   }

ISearchResponse<T> does expose how many shards succeeded and how many failed but does not expose the failure reason. <error message> may be something like IndexOutOfBoundsException[Index: 1, Size: 1].

Am I missing something here or is this really not supported by Nest1.0? If later, is there any plan to support this?

@Mpdreamz
Copy link
Member

Mpdreamz commented Sep 8, 2014

Thanks for reporting @bittusrk ! This has now been implemented.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants