# Index "not\_analyzed" for fields with type "object"

**URL:** https://discuss.elastic.co/t/index-not-analyzed-for-fields-with-type-object/3282
**Category:** Elasticsearch
**Created:** [August 31, 2010, 3:13pm UTC](https://discuss.elastic.co/t/index-not-analyzed-for-fields-with-type-object/3282 "2010-08-31T15:13:55Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Andrew\_Degtiariov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_degtiariov/32/3223_2.png) [@Andrew\_Degtiariov](https://discuss.elastic.co/u/Andrew_Degtiariov)
#### Post date: [August 31, 2010, 3:13pm UTC](https://discuss.elastic.co/t/index-not-analyzed-for-fields-with-type-object/3282/1 "2010-08-31T15:13:55Z")

</div>

Is there possible to specify "index": "not\_analyzed" for fields with  
type "object"?  
In mapping for document I want to include full object for omitting  
database queries:  
{  
"contact": {  
"properties" : {  
"serialized\_object": {  
"type": "object",  
"index": "not\_analyzed",  
"store": "yes"  
}  
}  
}

But when I requested mapping for the document from index I see then  
all fields in "serialized\_object" is in index "analyzed":  
{  
.....

```
          "serialized_object" : {
               "date_formats" : [
                  "dateOptionalTime", "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd"
                ],
              "dynamic" : true,
              "enabled" : true,
              "path" : "full",
              "properties" : {
                      "account_id" : {
                         "boost" : 1.0,
                         "index" : "analyzed",
                         "index_name" : "account_id",
                         "omit_norms" : false,
                         "omit_term_freq_and_positions" : false,
                         "store" : "no",
                         "term_vector" : "no",
                         "type" : "string"
                    },

                    .....
              },
    ...

```

## }

Andrew Degtiariov  
DA-RIPE

---

<div class="post-metadata">

### Author: ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)
#### Post date: [August 31, 2010, 6:18pm UTC](https://discuss.elastic.co/t/index-not-analyzed-for-fields-with-type-object/3282/2 "2010-08-31T18:18:41Z")

</div>

No, you will have to set the it for each field. There can be a feature, on  
the object level, where each mapping created that has no mapping defined for  
index (for example), then use the one defined on the object level.

-shay.banon

On Tue, Aug 31, 2010 at 6:13 PM, Andrew Degtiariov \<  
[andrew.degtiariov@gmail.com](mailto:andrew.degtiariov@gmail.com)\> wrote:

> Is there possible to specify "index": "not\_analyzed" for fields with  
> type "object"?  
> In mapping for document I want to include full object for omitting  
> database queries:  
> {  
> "contact": {  
> "properties" : {  
> "serialized\_object": {  
> "type": "object",  
> "index": "not\_analyzed",  
> "store": "yes"  
> }  
> }  
> }
> 
> But when I requested mapping for the document from index I see then  
> all fields in "serialized\_object" is in index "analyzed":  
> {  
> .....
> 
> ```
> "serialized_object" : {
> "date_formats" : [
> "dateOptionalTime", "yyyy/MM/dd HH:mm:ss||yyyy/MM/dd"
> ],
> "dynamic" : true,
> "enabled" : true,
> "path" : "full",
> "properties" : {
> "account_id" : {
> "boost" : 1.0,
> "index" : "analyzed",
> "index_name" : "account_id",
> "omit_norms" : false,
> "omit_term_freq_and_positions" : false,
> "store" : "no",
> "term_vector" : "no",
> "type" : "string"
> },
> 
> .....
> },
> ...
> 
> ```
> 
> ## }
> 
> Andrew Degtiariov  
> DA-RIPE

---

<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 6, 2017, 4:20am UTC](https://discuss.elastic.co/t/index-not-analyzed-for-fields-with-type-object/3282/3 "2017-07-06T04:20:00Z")

</div>