Skip to content

Add support for geo_shape_match enrich policy type #42639

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.

Sign up for GitHub

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

Jump to bottom
Closed
martijnvg opened this issue May 28, 2019 · 1 comment
Closed

Add support for geo_shape_match enrich policy type #42639

martijnvg opened this issue May 28, 2019 · 1 comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP

Comments

@martijnvg
Copy link
Member

This includes:

  • Adding geo_shape_match policy type to EnrichPolicy class.
  • Changing the policy running to be able to handle policies of type geo_shape_match. Query field in source index needs to be of type geo shape.
  • Creating an enrich processor that is able to execute a Lucene level geo shape query and for the matching docs extracts the enrich values and include these values to the document being ingested. The value in the document being ingested can be a geo point or geo shape.

Relates to #32789
@martijnvg martijnvg added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label May 28, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

@jakelandis jakelandis mentioned this issue May 28, 2019
Closed
55 tasks
talevy added a commit to talevy/elasticsearch that referenced this issue Sep 27, 2019
@talevy
Geo-Match Enrich Processor
840273e 
this commit introduces a geo-match enrich processor that looks up a specific
`geo_point` field in the enrich-index for all entries that have a geo_shape match field
that meets some specific relation criteria with the input field.

For example, the enrich index may contain documents with zipcodes and their respective
geo_shape. Ingesting documents with a geo_point field can be enriched with which zipcode
they associate according to which shape they are contained within.

this commit also refactors some of the MatchProcessor by moving a lot of the shared code to
AbstractEnrichProcessor.

Closes elastic#42639.
@talevy talevy mentioned this issue Sep 27, 2019
Merged
talevy added a commit to talevy/elasticsearch that referenced this issue Oct 7, 2019
@talevy
Geo-Match Enrich Processor (elastic#47243)
0bf7d2c 
this commit introduces a geo-match enrich processor that looks up a specific
`geo_point` field in the enrich-index for all entries that have a geo_shape match field
that meets some specific relation criteria with the input field.

For example, the enrich index may contain documents with zipcodes and their respective
geo_shape. Ingesting documents with a geo_point field can be enriched with which zipcode
they associate according to which shape they are contained within.

this commit also refactors some of the MatchProcessor by moving a lot of the shared code to
AbstractEnrichProcessor.

Closes elastic#42639.
@talevy talevy mentioned this issue Oct 7, 2019
Merged
talevy added a commit that referenced this issue Oct 7, 2019
@talevy
Geo-Match Enrich Processor (#47243) (#47701)
a17f394 
this commit introduces a geo-match enrich processor that looks up a specific
`geo_point` field in the enrich-index for all entries that have a geo_shape match field
that meets some specific relation criteria with the input field.

For example, the enrich index may contain documents with zipcodes and their respective
geo_shape. Ingesting documents with a geo_point field can be enriched with which zipcode
they associate according to which shape they are contained within.

this commit also refactors some of the MatchProcessor by moving a lot of the shared code to
AbstractEnrichProcessor.

Closes #42639.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@talevy @martijnvg @elasticmachine