[Maps] query error on document layer index missing filtered shape field

[bcamper]

I believe this is a regression related to #47171.

I have 3 document layers, and I use 1 layer to create a filter against another layer, with coordinates as the filtered field:

This creates a geo_shape filter using the indexed shape:

This then causes an error on the 3rd layer, which lacks a coordinates field (it has a geo_point field called location_geo):

This works properly on 7.4, and I verified that it works in the console when I use the old inline shape query method. I would have expected the indexed shape query to work with ignore_unmapped: true set (which it is), but that doesn't seem to be the case (perhaps I misunderstand how it's supposed to behave here though).

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[nreese]

geo_point can not use geo_shape query so that is why there is a failure.

This would have failed in 7.4 because the generated query was also a geo_shape query. The only thing
#47171 changed was using pre-indexed shape instead of passing geometry in the query

Elasticsearch team is working on adding geo_point support to geo_shape query so these type incompatibilities will go away in the future but the problem will always exist if the geo field names are different,

[nreese]

Maybe we could add an option in the drop down to "Apply to all" that would create a should clause that adds a filter for each geo field name and type paring. The problem is that this will include the geometry for each query if its not indexed in Elasticsearch and not querying against geo_shape field so it will increase the likely hood of #45521.

But I could see this being really useful for drawing filters since the geometry is small and #45521 is not an issue.

[bcamper]

geo_point can not use geo_shape query so that is why there is a failure.
This would have failed in 7.4 because the generated query was also a geo_shape query. The only thing #47171 changed was using pre-indexed shape instead of passing geometry in the query

It doesn't generate an error in 7.4 or in master though, when running the same query with an inline shape field. It just returns no results. That may not be intentional, but that's the behavior I observe.