Introduce geo support #154
Merged
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
- geo_shape and _point are now recognized.
bpintea
added
>feature
13 tasks
bpintea
added a commit
that referenced
this pull request
May 18, 2019
* minor comment note * add identification for geo types - geo_shape and _point are now recognized. (cherry picked from commit 9bff473)
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.
This PR adds initial support for the Geo types: shape and point.
The driver will now recognize the new data types and will allow piping through the data as fetched from Elasticsearch, WKT encoded.
Any 3rd party application that will want to work with the type can use their own library on top of ODBC. For existing apps, the driver will return the data as text.