# Is there any way to create an additional field without using Scripted field and Logstash?
**URL:** https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157
**Category:** Elasticsearch
**Created:** [July 2, 2018, 9:20am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157 "2018-07-02T09:20:08Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [July 2, 2018, 9:20am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/1 "2018-07-02T09:20:08Z")
Hi,
I am using ELK GA 6.3.0. In my index, there is a `number` attribute, currently taking as `string`. To perform aggregations, I have created a `number` scripted field like;
```
return doc['field_a'].value;
```
This works fine, but utilizes CPU. Is there any way to achieve the same, more efficiently, and without using Logstash?
Thanks.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 2, 2018, 9:56am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/2 "2018-07-02T09:56:58Z")
Yes, you can reindex your data and add a new field with correct mapping using the [reindex API together with a script or ingest pipeline](https://www.elastic.co/guide/en/elasticsearch/reference/6.3/docs-reindex.html). To add this on the ingest side for new data, create an ingest pipeline for this as well.
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [July 2, 2018, 11:17am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/3 "2018-07-02T11:17:08Z")
Thank you @Christian_Dahlqvist . Could you kindly show me some code to create a pipeline which convert `string` data in `field_a` to a number, and store it in `field_b` in the index `my_index-*`?
Thanks.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [July 2, 2018, 11:42am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/4 "2018-07-02T11:42:11Z")
Try a pipeline with e.g. a grok processor:
```auto
{
"processors" : [
{
"grok": {
"field": "field_a",
"patterns": ["%{NUMBER:field_b:int}"]
}
}
]
}
```
---
### Author:  [@elasticheart](https://discuss.elastic.co/u/elasticheart)
#### Post date: [July 2, 2018, 11:43am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/5 "2018-07-02T11:43:23Z")
Thanks Christian 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 30, 2018, 11:43am UTC](https://discuss.elastic.co/t/is-there-any-way-to-create-an-additional-field-without-using-scripted-field-and-logstash/138157/6 "2018-07-30T11:43:24Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.