# Fields added using a ruby filter doesn't survive split filter
**URL:** https://discuss.elastic.co/t/fields-added-using-a-ruby-filter-doesnt-survive-split-filter/57158
**Category:** Logstash
**Created:** [August 3, 2016, 10:28pm UTC](https://discuss.elastic.co/t/fields-added-using-a-ruby-filter-doesnt-survive-split-filter/57158 "2016-08-03T22:28:40Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@kaung](https://discuss.elastic.co/u/kaung)
#### Post date: [August 3, 2016, 10:28pm UTC](https://discuss.elastic.co/t/fields-added-using-a-ruby-filter-doesnt-survive-split-filter/57158/1 "2016-08-03T22:28:40Z")
I have a logstash config looking roughly like below:
```
#ruby <1>
ruby { code => "event['@metadata']['scheduledTime'] = Time.now" }
...
split {
field => "xxx"
target => "yyy"
}
...
#ruby <2>
ruby { code => " #read event['@metadata']['scheduledTime'] and do some calculation " }
```
Field added in ruby \<1\> are not carried to ruby\<2\>. Split filter cloning somehow doesn't carry these fields onward.
The same ruby filters without split between works fine.
Is there a different way to add fields in a ruby filter or is the issue is from split filter?
---
### Author:  [@kaung](https://discuss.elastic.co/u/kaung)
#### Post date: [August 4, 2016, 4:30am UTC](https://discuss.elastic.co/t/fields-added-using-a-ruby-filter-doesnt-survive-split-filter/57158/2 "2016-08-04T04:30:18Z")
Ok. Now I understand the issue.
- It has nothing to do with ruby or split filter
- the issue is actually @metadata fields are not copied when events are being cloned
- a defect is already reported and it is still "open"
[https://github.com/elastic/logstash/issues/4306](https://github.com/elastic/logstash/issues/4306)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 4:44am UTC](https://discuss.elastic.co/t/fields-added-using-a-ruby-filter-doesnt-survive-split-filter/57158/3 "2017-07-06T04:44:59Z")