Skip to content

Conversation

craigtaverner
Copy link
Contributor

Manual backport of #122886

The original work at elastic#106065 did not support geospatial types with this comment:

> I made this work for everything but geo_point and cartesian_point because I'm not 100% sure how to integrate with those. We can grab those in a follow up.

The geospatial types should be possible to collect using the VALUES aggregation with similar behavior to the `ST_COLLECT` OGC function, based on the Elasticsearch convention that treats multi-value geospatial fields as behaving similarly to any geometry collection. So this implementation is a trivial addition to the existing values types support.
@craigtaverner craigtaverner added >bug backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) :Analytics/ES|QL AKA ESQL v8.19.0 labels May 2, 2025
Copy link
Contributor

github-actions bot commented May 2, 2025

Documentation preview:

@craigtaverner craigtaverner merged commit fb0f93c into elastic:8.19 May 2, 2025
16 checks passed
drewdaemon pushed a commit to elastic/kibana that referenced this pull request May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/ES|QL AKA ESQL backport >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v8.19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants