Support Spatial Search in ES|QL (ST_INTERSECTS, ST_CONTAINS, ST_WITHIN and ST_DISJOINT)

[craigtaverner]

Description

The spatial search in Elasticsearch is directly backed by Lucene for four cases:

• Intersects
• Contains
• Within
• Disjoint

These can be exposed in ES|QL through four OGC compliant functions:

• boolean ST_INTERSECTS(geomA, geomB)
• boolean ST_CONTAINS(geomA, geomB)
• boolean ST_WITHIN(geomA, geomB)
• boolean ST_DISJOINT(geomA, geomB)

For example:

FROM airports
| EVAL polygon = TO_GEOSHAPE("POLYGON((...))")
| WHERE ST_INTERSECTS(location, polygon)

See the PostGIS documentation for inspiration: https://postgis.net/docs/ST_Intersects.html

The feature can be developed in several phases:

• Bring back Intersects prototype prototype from last summer
  • Expects constant string WKT
  • Does in-memory constant->triangle-tree and then internal intersects
• Support all kinds of fields (source, doc-values, constants, geo/cartesian, point/shape)
• LocalPhysicalPlanner support for push-down to Lucene
  • Handle special cases regarding cartesian data (not fully supported in Elasticsearch)

Tasks

Beta Give feedback

1. Bring back prototype from last summer (geo_point in polygon)
2. Support cartesian point in polygon
3. Support polyon intersects polygon
4. Support any geometry intersects any geometry
5. Support doc-values for point in polygon
6. Support doc-values for geometry intersects geometry
7. Support CONTAINS and WITHIN (keep in mind inverse commutative relationship for pushdown)
8. Support DISJOINT (special need for handling Cartesian, which Elasticsearch does not handle completely)
9. Documentation

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)

[nik9000]

At least they all start with ST_!