-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new geo
module and migrate geo_shape registration
#53562
Conversation
This commit introduces a new spatial-extras module that is intended to be contain all the geo-spatial-specific features in server. As a first step, the responsibility of registering the geo_shape field mapper is moved to this module.
Pinging @elastic/es-analytics-geo (:Analytics/Geo) |
@@ -52,7 +52,7 @@ protected void initializeAdditionalMappings(MapperService mapperService) throws | |||
|
|||
@Override | |||
protected Collection<Class<? extends Plugin>> getPlugins() { | |||
return Collections.singleton(MapperExtrasPlugin.class); | |||
return List.of(MapperExtrasPlugin.class, TestGeoShapeFieldMapperPlugin.class); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is room to pull the TestGeoShapeFieldMapperPlugin
to the parent test class and inherited by those that need it or need to extend to include more plugins. I could see it stay either way since it is fairly low impact and the dependency is expected to go away
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a couple questions/suggestions
.../mapper-extras/src/test/java/org/elasticsearch/index/query/RankFeatureQueryBuilderTests.java
Outdated
Show resolved
Hide resolved
modules/spatial-extras/src/main/java/org/elasticsearch/spatial/SpatialExtrasPlugin.java
Outdated
Show resolved
Hide resolved
@elasticmachine update branch |
merge conflict between base and head |
geo
module and migrate geo_shape registration
thanks for pushing those changes to the branch @nknize, I'll get the CI happy from here on out! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! It will be nice to have a place where we can actually start migrating geo stuff into a module.
thanks Ryan! |
) (#54924) This commit introduces a new `geo` module that is intended to be contain all the geo-spatial-specific features in server. As a first step, the responsibility of registering the geo_shape field mapper is moved to this module. Co-authored-by: Nicholas Knize <[email protected]>
After elastic#53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
After #53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
…#55500) After #53562, the `geo_shape` field mapper is registered within a module. This opens the door for introducing a new `geo_shape` field mapper into the Spatial Plugin that has doc-values support. This is very much an extension of server's GeoShapeFieldMapper, but with the addition of the doc values implementation.
This commit introduces a new
geo
module that is intendedto contain all the geo-spatial-specific features in server.
As a first step, the responsibility of registering the geo_shape
field mapper is moved to this module.