Override doc_values parameter in Spatial XPack Module #53263
Labels
:Analytics/Geo
Indexing, search aggregations of geo points and shapes
Team:Analytics
Meta label for analytical engine team (ESQL/Aggs/Geo)
In support of the upcoming geo_shape doc values and aggregation feature (licensed Basic). The
doc_values
field mapper parameter needs to be available in bothGeoShapeFieldMapper
andShapeFieldMapper
when the spatial xpack module is loaded, and the basic license is available. If the spatial xpack module is not available, existing OSS behavior should remain the same (e.g.,MapperParsingException
whendoc_values
parameter is explicitly provided by the user).This issue will capture discussion and track progress on the design and implementation for overriding
doc_values
field mapper parameter through the Spatial x-pack module.The Spatial Doc Value Parameter Feature Branch is available for review and discussion and provides the following behavior:
doc_values
parameter defaults totrue
forGeoShapeFieldMapper
andShapeFieldMapper
doc_values
parameter throws an Exception for newgeo_shape
fields defined using the legacy PrefixTree indexing approach (same behavior as before)doc_values
parameter defaults tofalse
forGeoShapeFieldMapper
andShapeFieldMapper
(same behavior as before)doc_values
parameter throws aMapperParsingException
(same behavior as before)The behavior is achieved using the following "hack":
GeoShapeFieldMapper.Extension
is loaded through SPI that overrides theGeometryIndexer
that adds theindexDocValues
logicAbstractGeometryFieldMapper.ParserExtension
is loaded through SPI that supplementsTypeParser.parse
logic to parse thedoc_values
parameter in the spatial xpack moduleIndicesModule.java
is "hacked" to load theParserExtension
andDataLoader
objects from xpack that provides the overriding behavior described aboveThe text was updated successfully, but these errors were encountered: