# Mutate rename issue after upgrade

**URL:** https://discuss.elastic.co/t/mutate-rename-issue-after-upgrade/274558
**Category:** Logstash
**Created:** [June 1, 2021, 1:20am UTC](https://discuss.elastic.co/t/mutate-rename-issue-after-upgrade/274558 "2021-06-01T01:20:42Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)
#### Post date: [June 1, 2021, 1:28am UTC](https://discuss.elastic.co/t/mutate-rename-issue-after-upgrade/274558/2 "2021-06-01T01:28:31Z")

</div>

> [@leandrojmp](#):
>
> ```auto
> rename => { "requestMethod" => "[http][request][method]"}
> rename => { "response_code" => "[http][response][status_code]"}
> 
> ```

Does it make any difference if you do

```
        rename => {
            "requestMethod" => "[http][request][method]"
            "response_code" => "[http][response][status_code]"
        }

```

I never use multiple instances of an option on a filter because very occasionally logstash combines them in unexpected ways.

---

_[View the full topic](https://discuss.elastic.co/t/mutate-rename-issue-after-upgrade/274558)._