forked from elastic/elasticsearch
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
SQL: Remove JDBC dependency on ES lib geo (elastic#82166)
As part of the effort of making JDBC driver self sufficient, remove the ES lib geo dependencies without any replacement. Currently the JDBC driver takes the WKT text and instantiates a geo object based on the ES lib geo. Moving forward the driver will return the WKT string representation without any conversion letting the user pick the geo library desired. That can be ES lib geo, jts, spatial4j or others. Note this is a breaking change. Relates elastic#80277
- Loading branch information
Showing
6 changed files
with
51 additions
and
37 deletions.
There are no files selected for viewing
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
27 changes: 27 additions & 0 deletions
27
docs/reference/migration/migrate_8_0/sql-jdbc-changes.asciidoc
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
[discrete] | ||
[[breaking_80_jdbc_changes]] | ||
==== SQL JDBC changes | ||
|
||
//NOTE: The notable-breaking-changes tagged regions are re-used in the | ||
//Installation and Upgrade Guide | ||
|
||
//tag::notable-breaking-changes[] | ||
.JDBC driver returns geometry objects as well-known-text string instead of `org.elasticsearch.geo` objects. | ||
[%collapsible] | ||
==== | ||
*Details* + | ||
To reduce the dependency of the JDBC driver onto Elasticsearch classes, the JDBC driver returns geometry data | ||
as strings using the WKT (well-known text) format instead of classes from the `org.elasticsearch.geometry`. | ||
Users can choose the geometry library desired to convert the string represantion into a full-blown objects | ||
either such as the `elasticsearch-geo` library (which returned the object `org.elasticsearch.geo` as before), | ||
jts or spatial4j. | ||
*Impact* + | ||
Before upgrading, replace any `org.elasticsearch.geo` classes on the `ResultSet#getObject` or `ResultSet#setObject` | ||
Elasticsearch JDBC driver with their WKT representation by simply calling `toString` or | ||
`org.elasticsearch.geometry.utils.WellKnownText#toWKT/fromWKT` methods. | ||
This change does NOT impact users that do not use geometry classes. | ||
==== | ||
// end::notable-breaking-changes[] |
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
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
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
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