Conversation
…ometry Change-Id: I3a88b45b021ec8d40bd6a479b6f17ed15a411d38
ramitg254
force-pushed
the
HIVE-29353
branch
from
September 23, 2026 05:55
dd40686 to
fc23fb3
Compare
|
This branch has not been deployed
This file contains hidden or 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
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.



Change-Id: I3a88b45b021ec8d40bd6a479b6f17ed15a411d38
What changes were proposed in this pull request?
Add basic support for encoding a geohash for a 2d point and decoding it to corresponding bounding box.
Why are the changes needed?
geohash encoding and decoding is not supported
Does this PR introduce any user-facing change?
Yes, user will be able to use st_geohash and st_geomfromgeohash spatial functions.
How was this patch tested?
unit test