mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
e00b354c26
With https://github.com/elastic/stack-docs/pull/2495 merged, we no longer reuse breaking changes in the Stack Install/Upgrade guide. This removes the related `notable-breaking-changes[]` tags from the 8.9+ docs and updates the RN generator template. ## Out of scope With the removal of these tags, we may no longer need the `notable` property for changelog entries and can likely simplify the logic for the [BreakingChangesGenerator](https://github.com/elastic/elasticsearch/blob/main/build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/release/BreakingChangesGenerator.java). Updating those files is outside the scope of this PR. I've opened https://github.com/elastic/elasticsearch/issues/98145 to track that work.
22 lines
1,021 B
Text
22 lines
1,021 B
Text
[discrete]
|
|
[[breaking_80_jdbc_changes]]
|
|
==== SQL JDBC 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 representation 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.
|
|
|
|
====
|