# Store field as text and keyword in 7.3

**URL:** <https://discuss.elastic.co/t/store-field-as-text-and-keyword-in-7-3/238520>\
**Category:** Elasticsearch\
**Created:** [June 24, 2020, 3:14pm UTC](https://discuss.elastic.co/t/store-field-as-text-and-keyword-in-7-3/238520 "2020-06-24T15:14:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeremy\_A](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jeremy_a/32/42598_2.png) [@Jeremy\_A](https://discuss.elastic.co/u/Jeremy_A)\
**Post date:** [June 24, 2020, 3:14pm UTC](https://discuss.elastic.co/t/store-field-as-text-and-keyword-in-7-3/238520/1 "2020-06-24T15:14:08Z")

</div>

I've recently migrated from 6.8 to 7.3 and noticed an apparent different in how Elasticsearch is handling my templates.  
Here's an excerpt from my index template:

```auto
    {
     "index_patterns": ["xxx-*"],
     "settings": {
       "number_of_shards": 1,
       "number_of_replicas": 1
     },
     "mappings": {
       "doc": {
         "properties": {
           "message": {
             "type": "text",
             "fields": {
               "keyword": {
                 "type": "keyword",
                 "ignore_above": 30000
               }
             }
           },
           "LAT-LONG": {
             "type": "text",
             "fields": {
               "keyword": {
                 "type": "geo_point"
               }
               
             }
           }
         }
       } 
     }
    }

```

Under 6.8, this resulted in the "message" field being stored as both message and message.keyword, and the "LAT-LONG" was stored as both LAT-LONG and LAT-LONG.keyword. Now, in 7.3, the ".keyword" fields are not being created. Is there something I need to change?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 25, 2020, 1:58am UTC](https://discuss.elastic.co/t/store-field-as-text-and-keyword-in-7-3/238520/2 "2020-06-25T01:58:36Z")

</div>

I'm not sure why you would want to store the original `LAT_LONG` value as `text`, just have it as a `geo_point`.

However I just tested this on 7.8, and it worked as per the mapping you provided.

---

<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 23, 2020, 1:58am UTC](https://discuss.elastic.co/t/store-field-as-text-and-keyword-in-7-3/238520/3 "2020-07-23T01:58:37Z")

</div>

Closed on July 23, 2020, 1:58am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.