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

[Feature Request][Ingest Pipeline] Adding a Copy processor #55682

Closed
P1llus opened this issue Apr 23, 2020 · 2 comments
Closed

[Feature Request][Ingest Pipeline] Adding a Copy processor #55682

P1llus opened this issue Apr 23, 2020 · 2 comments
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team

Comments

@P1llus
Copy link
Member

P1llus commented Apr 23, 2020

Describe the feature:

Currently it is not possible to copy a object to another object.

An example would be during ingestion, to populate all the source and destination ECS fields, and in plenty of use-cases these have to be copied to client/server fields as well.

Currently its not possible to use the set processor to set the value of the "client" object to the value of "source" object.

This combined with #54783 creates a situation in which we have to rely on a large amount of set + painless conditions for each and every field.

Source and Destination alone is large objects, so 30 fields would result in 30 set processors each with at least 1 painless script condition since we cannot check for null inside the processor.

If we was able to duplicate a object to a new object, and either copy it directly to root or define the path (if you want to copy it deeper than root) then it would create very big benefits for us when creating ingest pipelines.

@P1llus P1llus added the :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP label Apr 23, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Ingest)

@danhermann
Copy link
Contributor

Resolved by #63540

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 Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

4 participants