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

Check for failed shards in count #1444

Closed

Conversation

yogevyuval
Copy link

Fixes #1302 .

When some shards fail, the count is returned as a default or a partial answer, hiding the error from the user.

@yogevyuval
Copy link
Author

@sethmlarson

@yogevyuval
Copy link
Author

@tommyzli

@yogevyuval
Copy link
Author

@armando1793

@yogevyuval
Copy link
Author

@hugovk

@yogevyuval
Copy link
Author

@pquentin

@miguelgrinberg
Copy link
Collaborator

Unfortunately it is difficult to know how to handle shard failures. Automatically raising a failure is not always the correct option, to me it feels the best option would be to expose the information, so that each application can decide if and how many shards failing should be considered a failure.

Based on your description in #1302 you are sending queries that are bad, so in that case a returned count of 0 does not seem completely wrong.

So I'm going to close this PR, but will keep the issue open, as we need a way to expose the complete results of the count operation for applications that need to make decisions based on that.

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

Successfully merging this pull request may close these issues.

Count returns 0 and does not check for failed shards
2 participants