The ES|QL ENRICH command already supports exact match queries (based on the term query) for keyword field matches, however as described in the documentation on how to "enrich your data", there are three types of ENRICH supported by Elasticsearch ingest processors:
Ideally we would like ES|QL to support all the features supported by Elasticsearch ingest. In particular there have be specific requests to support CIDR_MATCH in ENRICH, which would be supported by the range enrich policy above.
Limitations:
One concern would be the geo_match which expects the shape_relation to be defined in the ingest processor, not the enrich policy, which would imply that the ENRICH command needs to be enhanced to support this. However, since the geo_match enrich policy defaults to intersects, it is possible to support this without enhancing the the command syntax, and consider that enhancement as a later feature.
Description
The ES|QL ENRICH command already supports exact match queries (based on the
term
query) forkeyword
field matches, however as described in the documentation on how to "enrich your data", there are three types of ENRICH supported by Elasticsearch ingest processors:term
queryterm
querygeo_shape
queryIdeally we would like ES|QL to support all the features supported by Elasticsearch ingest. In particular there have be specific requests to support CIDR_MATCH in ENRICH, which would be supported by the
range
enrich policy above.Limitations:
geo_match
which expects theshape_relation
to be defined in the ingest processor, not the enrich policy, which would imply that the ENRICH command needs to be enhanced to support this. However, since thegeo_match
enrich policy defaults tointersects
, it is possible to support this without enhancing the the command syntax, and consider that enhancement as a later feature.