# How to ignore properties in mapping
**URL:** https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840
**Category:** Elasticsearch
**Created:** [November 11, 2016, 7:38pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840 "2016-11-11T19:38:15Z")
**Posts on this page:** 17
**Page:** 1
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 11, 2016, 7:38pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/1 "2016-11-11T19:38:15Z")
Thanks in advance.
I'm retrieving my records from mongo, then using Node to insert into ES thru API.
here is a small part of my mapping
{
"price\_list\_tier": {
"dynamic": "static",
"properties": {
"sku": { "type": "string"},
"amount": { "type": "double"}
}
}
}
I have the following I'd like to insert (just a partial listing)
price\_list\_tier: {
sku: "lk38s38d38ck",
amount: 35.57,
upcharge: [{"size": "XL", "amount": 1}, {"size": "XXL", "amount": 1.25 }]
1. Node: when node sees the 1, it treats this as an integer. I then get a mapping error, trying to insert a long into a double. What's the best way to handle this?
2. I want to ignore completely the upcharge property, even if included in the object I send up for indexing. No matter what I have tried, I continue to get the mapping error trying to insert a long into double (upcharge.amount). Is it possible to skip the mapping of this property? I have tried:
a) using dynamic: static, and not defining upcharge.
b) upcharge: { "indexed": no, "enabled": no }
c) upcharge: { "type": "object", "dynamic": "static" }
I'm using Compose Elasticsearch 2.4.0
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 9:33am UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/2 "2016-11-14T09:33:14Z")
Hi @bwillis614,
ad 1: you need to handle this on the client side and convert the value explicitly to a double.
ad 2. You need to exclude this field from `_source` (see [docs](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/mapping-source-field.html#include-exclude)). Here is a complete example that should get you started:
```auto
DELETE /store
PUT /store
{
"mappings": {
"product": {
"_source": {
"excludes": ["upcharge"]
},
"properties": {
"product": {
"type": "string",
"index": "not_analyzed"
},
"amount": {
"type": "double"
},
"upcharge": {
"type": "object",
"enabled": false,
"include_in_all": false
}
}
}
}
}
PUT /store/product/1
{
"product": "p1",
"amount": 12.34,
"upcharge": [{"size": "XL", "amount": 1}, {"size": "XXL", "amount": 1.25 }]
}
GET /store/product/1
PUT /store/product/2
{
"product": "p2",
"amount": 22.34
}
GET /store/product/2
```
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 2:21pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/3 "2016-11-14T14:21:19Z")
Thank you so much.
I don't understand. I put the following in my mapping:
"price\_list\_tier": {
"\_source": {
"excludes": ["upcharge"]
},
"properties": {
"account\_id": {
"type": "string"
},
"upcharges": {
"type": "object",
"enabled": false,
"include\_in\_all": false
},
and now on upload I get:
[ { type: 'mapper\_parsing\_exception',
reason: 'failed to parse',
caused\_by:
{ type: 'illegal\_argument\_exception',
reason: 'mapper [upcharges.amount] of different type, current\_type
[double], merged\_type [long]' } },
{ type: 'mapper\_parsing\_exception',
reason: 'failed to parse',
caused\_by:
{ type: 'illegal\_argument\_exception',
reason: 'mapper [upcharges.amount] of different type, current\_type
[double], merged\_type [long]' } },
I was hoping that elasticSearch would completely ignore the field?
Is there a way to do that?
I thought by leaving the field out and putting this in that it would
completely ignore the field.
"price\_list\_tier": {
"dynamic": "static",
"properties": {
"dynamic": "static",
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 2:23pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/4 "2016-11-14T14:23:30Z")
Hi @bwillis614,
seems you have still documents in your index. If these are just test documents, just delete the index, recreate it with the new mapping and index your documents again. If you're in production, create a new index and use the reindex plugin to reindex your data.
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 2:32pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/5 "2016-11-14T14:32:34Z")
Even if the data was bad (I think Mongo/Node are feeding me ints for whole
numbers), is there a way to ingore these input fields that I don't want to
index, even if they are wrong expected type?
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 2:35pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/6 "2016-11-14T14:35:48Z")
I have dropped the index between runs. there's nothing there. it's my
data.
"upcharges" : [
{
"size" : "XXL",
"amount" : NumberInt(0)
},
{
"size" : "2XL",
"amount" : NumberInt(0)
},
{
"size" : "3XL",
"amount" : NumberInt(0)
},
{
"size" : "4XL",
"amount" : 2.5
},
{
"size" : "5XL",
"amount" : 2.5
}
],
I was hoping since I didn't want to index, it would just drop those fields
off, not even look at them, process rest of document?
It hasn't happened that way for me yet.
I'm using compose.elasticsearch.
Database _Elasticsearch 2.4.0_
Location _us-east-1_ on
_aws_
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 2:37pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/7 "2016-11-14T14:37:22Z")
there's a bug in some other code that we haven't deployed yet, to force
whole numbers to be doubles in mongo.
but for now, I wanted to make this work. elasticsearch accepting bad data,
ignoring those fields because they won't be indexed.
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 2:49pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/8 "2016-11-14T14:49:14Z")
ok, my last email. My latest attempt didn't work on disparate data either.
"price\_list\_tier": {
"\_source": {
"excludes": [
"upcharges",
"integrations.lemonstand.price\_tiers"
]
},
"upcharges": {
"type": "object",
"enabled": false,
"indexed": "no",
"include\_in\_all": false
},
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 2:57pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/9 "2016-11-14T14:57:45Z")
Hi @bwillis614,
there seems to be something wrong with your mapping or your data... . Can you provide a small, self-contained example (see my example above) that reproduces the problem you experience?
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 3:28pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/10 "2016-11-14T15:28:22Z")
Daniel, I attached two files, both in json format. I hope that is good
enough?
price\_list\_tier.json is my model.
dat\_to\_insert.json is my one row of data, with disparate array data types
in the field I'm hoping to completely ignore.
If that doesn't work for you, let me know and I'll comply. I haven't done
any direct posting, only api work thru node driver.
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 3:34pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/11 "2016-11-14T15:34:13Z")
Hi @bwillis614,
seems Discuss scrubbed the attachment. Can you provide them as gist or something similar?
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 3:52pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/12 "2016-11-14T15:52:38Z")
I'll try. hopefully I get this right.
```auto
DELETE /store
PUT /store
{
"mappings": {
"price_list_tier": {
"_source": {
"excludes": [
"upcharges",
"integrations.lemonstand.price_tiers"
]
},
"properties": {
"account_id": {
"type": "string"
},
"amount": {
"type": "double"
},
"created_on": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"integrations": {
"properties": {
"lemonstand": {
"properties": {
"last_sync": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"shop_customer_group_id": {
"type": "string"
},
"price_tiers": {
"type": "object",
"enabled": false,
"index": "no",
"include_in_all": false
}
}
}
}
},
"max_qty": {
"type": "long"
},
"min_qty": {
"type": "long"
},
"name": {
"type": "string"
},
"price_list_id": {
"type": "string"
},
"product_id": {
"type": "string"
},
"product_name": {
"type": "string"
},
"product_number": {
"type": "string"
},
"sku": {
"type": "string"
},
"type": {
"type": "string"
},
"upcharges": {
"type": "object",
"enabled": false,
"index": "no",
"include_in_all": false
},
"updated_on": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"variants": {
"type": "string"
}
}
}
}
}
PUT /store/price_list_tier/1
{
"_id": "581375b968943f0e98a6266e",
"name": "n1",
"variants": [
"*"
],
"upcharges": [
{
"size": "XXL",
"amount": 0
},
{
"size": "2XL",
"amount": 0
},
{
"size": "3XL",
"amount": 0
},
{
"size": "4XL",
"amount": 2.5
},
{
"size": "5XL",
"amount": 2.5
}
],
"min_qty": 1,
"max_qty": 1,
"type": "USD",
"amount": 3.7,
"created_on": "2016-10-13T12:18:59.172+0000",
"updated_on": null,
"integrations": {
"lemonstand": {
"last_sync": "2016-10-17T21:02:32.426+0000",
"price_tiers": [
{
"sku": "10847363052669",
"pricetier_id": 25142
}
],
"shop_customer_group_id": 22
}
},
"account_id": "127fe169-720e-4e4a-ba48-448e054d4ef2",
"price_list_id": "c7a224bc-67b4-d173-8df1-1d2dfe636890",
"product_id": "b2ffe54c-7fe6-17e9-1f4e-ce1826ec7a1b",
"product_number": "4400CY",
"sku": "10847363052669",
"product_name": "Creeper "
}
```
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 4:25pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/13 "2016-11-14T16:25:28Z")
Hi @bwillis614,
the example helped me reproduce the problem and I could also solve your original problem with mixed long double values this way.
The only change I made was here:
```auto
"upcharges": {
"type": "object",
"enabled": false,
"include_in_all": false,
"properties": {
"amount": {
"type": "double"
}
}
}
```
For reference, I'll also include the complete mapping:
```auto
PUT /price_list_tier
{
"mappings": {
"price_list_tier": {
"_source": {
"excludes": [
"upcharges",
"integrations.lemonstand.price_tiers"
]
},
"properties": {
"account_id": {
"type": "string"
},
"amount": {
"type": "double"
},
"created_on": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"integrations": {
"properties": {
"lemonstand": {
"properties": {
"last_sync": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"shop_customer_group_id": {
"type": "string"
},
"price_tiers": {
"type": "object",
"enabled": false,
"include_in_all": false
}
}
}
}
},
"max_qty": {
"type": "long"
},
"min_qty": {
"type": "long"
},
"name": {
"type": "string"
},
"price_list_id": {
"type": "string"
},
"product_id": {
"type": "string"
},
"product_name": {
"type": "string"
},
"product_number": {
"type": "string"
},
"sku": {
"type": "string"
},
"type": {
"type": "string"
},
"upcharges": {
"type": "object",
"enabled": false,
"include_in_all": false,
"properties": {
"amount": {
"type": "double"
}
}
},
"updated_on": {
"type": "date",
"format": "strict_date_optional_time||epoch_millis"
},
"variants": {
"type": "string"
}
}
}
}
}
```
With this change, I could add your document to the index without any problems:
```auto
POST /store/price_list_tier/581375b968943f0e98a6266e
{
"name": "n1",
"variants": [
"*"
],
"upcharges": [
{
"size": "XXL",
"amount": 0
},
{
"size": "2XL",
"amount": 0
},
{
"size": "3XL",
"amount": 0
},
{
"size": "4XL",
"amount": 2.5
},
{
"size": "5XL",
"amount": 2.5
}
],
"min_qty": 1,
"max_qty": 1,
"type": "USD",
"amount": 3.7,
"created_on": "2016-10-13T12:18:59.172+0000",
"updated_on": null,
"integrations": {
"lemonstand": {
"last_sync": "2016-10-17T21:02:32.426+0000",
"price_tiers": [
{
"sku": "10847363052669",
"pricetier_id": 25142
}
],
"shop_customer_group_id": 22
}
},
"account_id": "127fe169-720e-4e4a-ba48-448e054d4ef2",
"price_list_id": "c7a224bc-67b4-d173-8df1-1d2dfe636890",
"product_id": "b2ffe54c-7fe6-17e9-1f4e-ce1826ec7a1b",
"product_number": "4400CY",
"sku": "10847363052669",
"product_name": "Creeper "
}
```
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 4:49pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/14 "2016-11-14T16:49:20Z")
thanks for all the help. This must be a node/driver issue. I still get
the error.
Index price\_list\_tier does not exist, attempting to create
mapping:
{"price\_list\_tier":{"\_source":{"excludes":["upcharges","integrations.lemonstand.price\_tiers"]},"properties":{"account\_id":{"type":"string"},"amount":{"type":"double"},"created\_on":{"type":"date","format":"strict\_date\_optional\_time||epoch\_millis"},"integrations":{"properties":{"lemonstand":{"properties":{"last\_sync":{"type":"date","format":"strict\_date\_optional\_time||epoch\_millis"},"shop\_customer\_group\_id":{"type":"string"},"price\_tiers":{"type":"object","enabled":false,"index":"no","include\_in\_all":false}}}}},"max\_qty":{"type":"long"},"min\_qty":{"type":"long"},"name":{"type":"string"},"price\_list\_id":{"type":"string"},"product\_id":{"type":"string"},"product\_name":{"type":"string"},"product\_number":{"type":"string"},"sku":{"type":"string"},"type":{"type":"string"},
_"upcharges":{"type":"object","enabled":false,"include\_in\_all":false,"properties":{"amount":{"type":"double"}}}_
,"updated\_on":{"type":"date","format":"strict\_date\_optional\_time||epoch\_millis"},"variants":{"type":"string"}}}}
Successfully created index price\_list\_tier
[ { type: 'mapper\_parsing\_exception',
reason: 'failed to parse',
caused\_by:
{ type: 'illegal\_argument\_exception',
reason: 'mapper [upcharges.amount] of different type, current\_type
[long], merged\_type [double]' } },
{ type: 'mapper\_parsing\_exception',
reason: 'failed to parse',
caused\_by:
{ type: 'illegal\_argument\_exception',
reason: 'mapper [upcharges.amount] of different type, current\_type
[long], merged\_type [double]' } } ]
---
### Author:  [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)
#### Post date: [November 14, 2016, 5:02pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/15 "2016-11-14T17:02:47Z")
Hi @bwillis614,
bummer. It worked fine in [Console](https://www.elastic.co/guide/en/kibana/5.0/console-kibana.html). Did you try it there too?
> [@bwillis614](#):
>
> Index price\_list\_tier does not exist, attempting to create
That's weird. Is your index name really `price_list_tier`? In the example above it was called `store`.
Daniel
---
### Author:  [@bwillis614](https://discuss.elastic.co/u/bwillis614)
#### Post date: [November 14, 2016, 5:16pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/16 "2016-11-14T17:16:51Z")
yeah, i cheated. I took your original reply and pasted my stuff into it.
I just missed that part. Index = price\_list\_tier.
I have not tried in console. just node/driver.
I haven't had issues with my other mappings, just this one. I'm assuming
because of disparate upcharges.amount types.
I see my other field at root level also named amount, but shares type of
double, which is desired.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 12, 2016, 5:17pm UTC](https://discuss.elastic.co/t/how-to-ignore-properties-in-mapping/65840/17 "2016-12-12T17:17:06Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.