PS-9121 Innodb fails to update spatial index #5276
Closed
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
https://perconadev.atlassian.net/browse/PS-9121 When a spatial index is used on a geomtery column which contains values with more precision, the comparison of minimum bounding rectangle(MBR) for the geometric values can result in unexpected errors because of trunation/rounding of data. Since the underlying data type used for representing the coordinates of MBR is double, it supports upto 15 digits after the decimal place and any data after after those digits is subject to rounding and truncated. So, the MBR comparison method borrowed from boost libaries is updated to hanlde comparisons upto 20 digits after the decimal place since the secondary index update relies on this comparison.
|
Name of the branch was wrong. |
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.
https://perconadev.atlassian.net/browse/PS-9121
When a spatial index is used on a geomtery column which contains values with more precision, the comparison of minimum bounding rectangle(MBR) for the geometric values can result in unexpected errors because of trunation/rounding of data.
Since the underlying data type used for representing the coordinates of MBR is double, it supports upto 15 digits after the decimal place and any data after after those digits is subject to rounding and truncated.
So, the MBR comparison method borrowed from boost libaries is updated to hanlde comparisons upto 20 digits after the decimal place since the secondary index update relies on this comparison.