Skip to content
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

Merged
merged 27 commits into from
Apr 7, 2020

Conversation

talevy
Copy link
Contributor

@talevy talevy commented Mar 13, 2020

This commit introduces a new geo module that is intended
to 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.

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.
@talevy talevy added :Analytics/Geo Indexing, search aggregations of geo points and shapes >refactoring labels Mar 13, 2020
@talevy talevy requested review from rjernst and nknize March 13, 2020 20:23
@elasticmachine
Copy link
Collaborator

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);
Copy link
Contributor Author

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

Copy link
Member

@rjernst rjernst left a 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

@nknize
Copy link
Contributor

nknize commented Mar 18, 2020

@elasticmachine update branch

@elasticmachine
Copy link
Collaborator

merge conflict between base and head

@talevy talevy changed the title Create new spatial-extras module and migrate geo_shape registration Create new geo module and migrate geo_shape registration Mar 31, 2020
@talevy
Copy link
Contributor Author

talevy commented Mar 31, 2020

thanks for pushing those changes to the branch @nknize, I'll get the CI happy from here on out!

Copy link
Member

@rjernst rjernst left a 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.

@talevy
Copy link
Contributor Author

talevy commented Apr 7, 2020

thanks Ryan!

@talevy talevy merged commit cf9603c into elastic:master Apr 7, 2020
@talevy talevy deleted the spatial-extras branch April 7, 2020 19:27
talevy added a commit that referenced this pull request Apr 7, 2020
) (#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]>
talevy added a commit to talevy/elasticsearch that referenced this pull request Apr 10, 2020
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.
talevy added a commit that referenced this pull request Apr 16, 2020
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.
talevy added a commit that referenced this pull request Apr 22, 2020
…#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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Geo Indexing, search aggregations of geo points and shapes >refactoring v7.8.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants