Field "total_rows" is handled as "long" instead of "int" #242
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…esponses are parsed. When the database has a large number of documents (really large, around 2500 million documents), queries may crash with an "integer out of range" kind of error.
|
the pom versions should not be changed from SNAPSHOT |
YannRobert
requested changes
Mar 15, 2017
|
My fault. Pom files has been updated. Thank you and best regards. |
YannRobert
approved these changes
May 9, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the database has a large number of documents (around 2500 million documents), the parsing of a query response may crash with an "integer out of range" kind of error, because the content of "total_rows" exceeds the max value for an integer variable.