# Config'd mapping does not seem to take effect - part 2

**URL:** <https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708>\
**Category:** Elasticsearch\
**Created:** [May 15, 2012, 5:34pm UTC](https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708 "2012-05-15T17:34:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchgirl](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@searchgirl](https://discuss.elastic.co/u/searchgirl)\
**Post date:** [May 15, 2012, 5:34pm UTC](https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708/1 "2012-05-15T17:34:33Z")

</div>

Since I can't edit nor comment on my last post, I am posting  
additional information here. Please read the last post first.....

I modified my code to a put mapping before creating the index:

client.admin().indices().putMapping(Requests.putMappingRequest("en").source(indexConfigStr).type("product"));  
client.admin().indices().prepareCreate(en).execute().actionGet();

```
 "indexConfigStr" is "product.json" file content (see last post).

```

I query the mapping "[http://localhost:9200/en/product/\_mapping](http://localhost:9200/en/product/_mapping)", I  
now see the mapping:

{  
product: {  
properties: {

descl: {  
type: "string"  
},  
descs: {  
type: "string",  
boost: 1.3  
},  
pgrp: {  
type: "string",  
index: "not\_analyzed",  
store: "yes"  
},  
pid: {  
type: "string",  
index: "not\_analyzed",  
store: "yes"  
},  
rid: {  
type: "string",  
index: "not\_analyzed",  
store: "yes"  
},  
}  
}

It seems "store":"no" is the default. However, when getting a  
document, I still get the fields that are not suppose to be stored as  
text:

{  
\_index: "en",  
\_type: "product",  
\_id: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
\_version: 8,  
exists: true,  
\_source: {  
pid: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
rid: "44fe535f-4531-48bd-82d1-d96b6ef2bbe7",  
descl: "The Way Home",  
descs: "The Way Home",  
}  
}

So what does "store":"no" suppose to mean? Also, how can I verify  
boost factor at a field level is working? Thanks for your help in  
advance.

---

<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:** [May 15, 2012, 11:20pm UTC](https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708/2 "2012-05-15T23:20:31Z")

</div>

Although the fields are not being stored (which is the default), the  
original source document is. What you are viewing the the source and  
not the stored fields. You can change this behavior by disabling (or  
compressing) source:

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

--  
Ivan

On Tue, May 15, 2012 at 10:34 AM, Helen Poon [helenchenpoon@gmail.com](mailto:helenchenpoon@gmail.com) wrote:

> Since I can't edit nor comment on my last post, I am posting  
> additional information here. Please read the last post first.....
> 
> I modified my code to a put mapping before creating the index:
> 
> client.admin().indices().putMapping(Requests.putMappingRequest("en").source(indexConfigStr).type("product"));  
> client.admin().indices().prepareCreate(en).execute().actionGet();
> 
> ```
> "indexConfigStr" is "product.json" file content (see last post).
> 
> ```
> 
> I query the mapping "[http://localhost:9200/en/product/\_mapping](http://localhost:9200/en/product/_mapping)", I  
> now see the mapping:
> 
> {  
> product: {  
> properties: {
> 
> descl: {  
> type: "string"  
> },  
> descs: {  
> type: "string",  
> boost: 1.3  
> },  
> pgrp: {  
> type: "string",  
> index: "not\_analyzed",  
> store: "yes"  
> },  
> pid: {  
> type: "string",  
> index: "not\_analyzed",  
> store: "yes"  
> },  
> rid: {  
> type: "string",  
> index: "not\_analyzed",  
> store: "yes"  
> },  
> }  
> }
> 
> It seems "store":"no" is the default. However, when getting a  
> document, I still get the fields that are not suppose to be stored as  
> text:
> 
> {  
> \_index: "en",  
> \_type: "product",  
> \_id: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
> \_version: 8,  
> exists: true,  
> \_source: {  
> pid: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
> rid: "44fe535f-4531-48bd-82d1-d96b6ef2bbe7",  
> descl: "The Way Home",  
> descs: "The Way Home",  
> }  
> }
> 
> So what does "store":"no" suppose to mean? Also, how can I verify  
> boost factor at a field level is working? Thanks for your help in  
> advance.

---

<div class="post-metadata">

**Author:** ![searchgirl](https://avatars.discourse-cdn.com/v4/letter/s/e9a140/32.png) [@searchgirl](https://discuss.elastic.co/u/searchgirl)\
**Post date:** [May 16, 2012, 6:28pm UTC](https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708/3 "2012-05-16T18:28:30Z")

</div>

"store:no" fields are still returned with a "Get".

I found the following question. It looks like a fix to not show these  
fields in \_source from translog is to be included in 0.19.4. I am  
using 0.19.3.

[http://groups.google.com/group/elasticsearch/browse\_frm/thread/10e54cdec7dd6bca/8b4dc87d6b05d538?lnk=gst&q=\_source#8b4dc87d6b05d538](http://groups.google.com/group/elasticsearch/browse_frm/thread/10e54cdec7dd6bca/8b4dc87d6b05d538?lnk=gst&q=_source#8b4dc87d6b05d538)

On May 15, 7:20 pm, Ivan Brusic [i...@brusic.com](mailto:i...@brusic.com) wrote:

> Although the fields are not being stored (which is the default), the  
> original source document is. What you are viewing the the source and  
> not the stored fields. You can change this behavior by disabling (or  
> compressing) source:
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/mapping/source-field.html)
> 
> --  
> Ivan
> 
> On Tue, May 15, 2012 at 10:34 AM, Helen Poon [helenchenp...@gmail.com](mailto:helenchenp...@gmail.com) wrote:
> 
> > Since I can't edit nor comment on my last post, I am posting  
> > additional information here. Please read the last post first.....
> 
> > I modified my code to a put mapping before creating the index:
> 
> > client.admin().indices().putMapping(Requests.putMappingRequest("en").source (indexConfigStr).type("product"));  
> > client.admin().indices().prepareCreate(en).execute().actionGet();
> 
> > ```
> > "indexConfigStr" is "product.json" file content (see last post).
> > 
> > ```
> 
> > I query the mapping "[http://localhost:9200/en/product/\_mapping](http://localhost:9200/en/product/_mapping)", I  
> > now see the mapping:
> 
> > {  
> > product: {  
> > properties: {
> 
> > descl: {  
> > type: "string"  
> > },  
> > descs: {  
> > type: "string",  
> > boost: 1.3  
> > },  
> > pgrp: {  
> > type: "string",  
> > index: "not\_analyzed",  
> > store: "yes"  
> > },  
> > pid: {  
> > type: "string",  
> > index: "not\_analyzed",  
> > store: "yes"  
> > },  
> > rid: {  
> > type: "string",  
> > index: "not\_analyzed",  
> > store: "yes"  
> > },  
> > }  
> > }
> 
> > It seems "store":"no" is the default. However, when getting a  
> > document, I still get the fields that are not suppose to be stored as  
> > text:
> 
> > {  
> > \_index: "en",  
> > \_type: "product",  
> > \_id: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
> > \_version: 8,  
> > exists: true,  
> > \_source: {  
> > pid: "58d2ccf1-abc6-4a61-9eca-7c4d342b48c8",  
> > rid: "44fe535f-4531-48bd-82d1-d96b6ef2bbe7",  
> > descl: "The Way Home",  
> > descs: "The Way Home",  
> > }  
> > }
> 
> > So what does "store":"no" suppose to mean? Also, how can I verify  
> > boost factor at a field level is working? Thanks for your help in  
> > advance.

---

<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, 3:28am UTC](https://discuss.elastic.co/t/configd-mapping-does-not-seem-to-take-effect-part-2/7708/4 "2017-07-06T03:28:32Z")

</div>