-
Notifications
You must be signed in to change notification settings - Fork 101
Add geo-grid ingest processor #2844
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
Conversation
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
geojson, | ||
wkt |
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.
While the documentation says it should be GeoJSON
and WKT
, the YAML tests are using geojson
and wkt
. I talked to @craigtaverner who confirms that this processor was specifically designed to be case-insensitive so lowercase is OK.
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.
Nice, more processors 🙌
ignore_missing?: boolean | ||
/** | ||
* Which format to save the generated polygon in. | ||
* @server_default GeoJSON |
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.
Let's use full lowercase here as well to match the enum value.
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.
Oops! Done in b7eaafb
(#2844).
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
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! Thank you!
(cherry picked from commit e171d9f)
While this does not turn any status to green, this fixes most of the currently reported errors for
ingest.put_pipeline
requests.