Mutate rename multiple fields, how to improve performance?

[leandrojmp (Leandro Pereira)]

Hello,

I have a pipeline where I need to rename something around 1100 fields, the documents do not have all the fields, but in total I need to rename near 1100 fields.

Currently I have one mutate filter with a rename action for every field.

mutate {
    rename => { "field1" => "newField1"}
    rename => { "field2" => "newField2"}
    ...
    rename => { "fieldN" => "newFieldN"}
}

Would using one mutate filter and one rename action with the fields make any difference? Or in the end it will be the same thing?

mutate {
    rename {
        "field1" => "newField1"
        "field2" => "newField2"
        "fieldN" => "newFieldN"
    }
}

Anyone has a similar use case?

[Badger]

@leandrojmp

Or in the end it will be the same thing?

If there are multiple instances of an option on a filter they are merged when the configuration is parsed, so the two would be equivalent.