# Return substring of analyzed, non-stored text field
**URL:** https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231
**Category:** Elasticsearch
**Created:** [April 21, 2017, 3:50pm UTC](https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231 "2017-04-21T15:50:23Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@jdpark](https://discuss.elastic.co/u/jdpark)
#### Post date: [April 21, 2017, 3:50pm UTC](https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231/1 "2017-04-21T15:50:23Z")
Hi. I'd like to get the first 100 characters of an analyzed, non-stored text field. (Imagine I'm doing fulltext search on documents, and I want to return the documents with just snippets.) I read [https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting-fields.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting-fields.html). I considered the following options:
1. doc-values: I don't think I can use doc-values because it's an analyzed text field. (Enabling fielddata seems expensive and doesn't seem to fit in this use case).
2. stored fields: I'm currently not storing the text field
3. \_source: this option seems ok
The following GET works where "text" is the text field.
```auto
{
"script_fields": {
"substring": {
"script": {
"lang": "painless",
"inline": "params._source.text.substring(0, 100)"
}
}
}
}
```
Is this the right approach to this scenario? Or should I consider enabling fielddata so that I can use doc-values? Thank you.
---
### Author:  [@polyfractal](https://discuss.elastic.co/u/polyfractal)
#### Post date: [April 28, 2017, 1:54pm UTC](https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231/2 "2017-04-28T13:54:15Z")
Hm, so some caveats here.
As you mentioned, Doc values won't work with analyzed text fields... it's only available for `keyword` (not analyzed) text fields. The advantage of using `keyword` is that you can configure normalizers to do some basic analysis, such as lowercasing. And you get the speed benefits of having the data in doc values.
If you go down this route, the best option probably to add a multi-field which is set to `keyword`, with the inverted index disabled (`"index": "no"`) and keeping doc values enabled (`"doc_values": true`). As a downside, you'll pay the price of indexing another field w/ doc values (more on-disk usage, impact indexing speed, etc).
OTOH, the approach you're using with `_source` will work just fine... except it is not retrieving the analyzed text either. The `_source` is stored verbatim from the original JSON document that you sent to Elasticsearch. So it will represent a pre-analyzed version of the text.
If that's OK with you, the `_source` option is likely the best so long as your search requests only retrieve reasonably small result sets (10, 100, etc. but not 10,000).
Could you perhaps use/abuse the Highlighters to return the desired fragments? Highlighters perform analysis before returning the fragment, so they may be better suited if you need the analyzed text.
---
### Author:  [@jdpark](https://discuss.elastic.co/u/jdpark)
#### Post date: [May 8, 2017, 5:12pm UTC](https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231/3 "2017-05-08T17:12:38Z")
Hi Zachary. Thanks for the detailed response! I am actually using highlighters as well. I should clarify the above use case is really to generate document titles where the original source doesn't have one. Once the user clicks on one of the "titles", then the full document is shown with highlighting and other nested data.
Your note about multi-field is interesting and I'll keep it in mind to see if I can apply it somewhere else in the future. Thanks for the tip.
My question is answered, but a more "root cause" question is: is there a good way to generate document titles? I'm not expecting one from Elasticsearch, but just wondering if other users have come across this problem. Thanks readers.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 5, 2017, 5:21pm UTC](https://discuss.elastic.co/t/return-substring-of-analyzed-non-stored-text-field/83231/4 "2017-06-05T17:21:47Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.