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

Conditional pipeline processors #21248

Closed
niemyjski opened this issue Nov 1, 2016 · 4 comments · Fixed by #32398
Closed

Conditional pipeline processors #21248

niemyjski opened this issue Nov 1, 2016 · 4 comments · Fixed by #32398
Assignees
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >feature help wanted adoptme

Comments

@niemyjski
Copy link
Contributor

I wish there was a way to do some very basic conditional pipeline actions without going straight to scripts. For example, run this pipeline only if this field exists. I don't want to have to specify a failure action when a field doesn't exist....

            var response = await Configuration.Client.PutPipelineAsync(Pipeline, d => d
                .Processors(p => p
                    .Lowercase<Employee>(l => l.Field(f => f.Name))
                    .Trim<Employee>(t => t.Field(f => f.Name))
                ).OnFailure(of => of.Set<Employee>(s => s.Field(f => f.Name).Value(String.Empty))));
@niemyjski niemyjski changed the title Conditional pipelines Conditional pipeline processors Nov 1, 2016
@cbuescher cbuescher added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Nov 2, 2016
@clintongormley
Copy link
Contributor

@niemyjski
Copy link
Contributor Author

I didn't see that, and will take a look into it, but it still would be super nice to be able to some basic stuff like maybe check if a value was specified and if it doesn't specify defaults or run different processors on the field.

@talevy talevy added >feature help wanted adoptme :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP and removed >enhancement discuss :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP labels Mar 15, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@original-brownbear original-brownbear self-assigned this Jul 24, 2018
original-brownbear added a commit that referenced this issue Aug 30, 2018
* Ingest: Add conditional per processor
* closes #21248
original-brownbear added a commit to original-brownbear/elasticsearch that referenced this issue Sep 4, 2018
* Ingest: Add conditional per processor
* closes elastic#21248
original-brownbear added a commit that referenced this issue Sep 4, 2018
* Ingest: Add conditional per processor
* closes #21248
@nicholasyin
Copy link

Why wasn't this property added to every type of processor?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >feature help wanted adoptme
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants