# Delete me

**URL:** <https://discuss.elastic.co/t/delete-me/41508>\
**Category:** Elasticsearch\
**Created:** [February 11, 2016, 4:02pm UTC](https://discuss.elastic.co/t/delete-me/41508 "2016-02-11T16:02:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![basiclaser](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/basiclaser/32/23304_2.png) [@basiclaser](https://discuss.elastic.co/u/basiclaser)\
**Post date:** [February 11, 2016, 4:02pm UTC](https://discuss.elastic.co/t/delete-me/41508/1 "2016-02-11T16:02:53Z")

</div>

This was a non-issue which i have solved.

---

<div class="post-metadata">

**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\
**Post date:** [February 11, 2016, 5:18pm UTC](https://discuss.elastic.co/t/delete-me/41508/2 "2016-02-11T17:18:02Z")

</div>

You would need to sort against a field that has not been analyzed, or at  
least not tokenized (filters such as lowercase will still emit one token).  
Technically, you can sort using a script that pulls the non-analyzed data  
from the source, but it would be a big performance hit. Do not do it (I  
should have not even mentioned it!)

If you still need the text to be analyzed for search, look into using  
multi-fields, which is ideal in this scenario:

[https://www.elastic.co/guide/en/elasticsearch/reference/2.x/multi-fields.html](https://www.elastic.co/guide/en/elasticsearch/reference/2.x/multi-fields.html)

Note, your content will be to be reindexed.

Ivan

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:17pm UTC](https://discuss.elastic.co/t/delete-me/41508/3 "2017-07-05T23:17:05Z")

</div>

Closed on July 5, 2017, 11:17pm UTC