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

Support unknown fields in ingest pipeline map configuration #38352

Merged

Conversation

dakrone
Copy link
Member

@dakrone dakrone commented Feb 4, 2019

We already support unknown objects in the list of pipelines, this changes the
PipelineConfiguration to support fields other than just id and config.

Relates to #36938

We already support unknown objects in the list of pipelines, this changes the
`PipelineConfiguration` to support fields other than just `id` and `config`.

Relates to elastic#36938
@dakrone dakrone added >bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v7.0.0 v6.7.0 labels Feb 4, 2019
@dakrone dakrone requested a review from hub-cap February 4, 2019 18:11
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features

Copy link
Contributor

@hub-cap hub-cap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm assuming ci is happy :)

@dakrone
Copy link
Member Author

dakrone commented Feb 4, 2019

@elasticmachine run elasticsearch-ci/2

@dakrone dakrone merged commit d862453 into elastic:master Feb 5, 2019
dakrone added a commit to dakrone/elasticsearch that referenced this pull request Feb 5, 2019
…38352)

We already support unknown objects in the list of pipelines, this changes the
`PipelineConfiguration` to support fields other than just `id` and `config`.

Relates to elastic#36938
dakrone added a commit that referenced this pull request Feb 5, 2019
Backport of #38352

We already support unknown objects in the list of pipelines, this changes the
`PipelineConfiguration` to support fields other than just `id` and `config`.

Relates to #36938
@dakrone dakrone deleted the get-pipeline-response-ignore-fields branch February 14, 2019 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP v6.7.0 v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants