# MapperParsingException on percolation with \_size enabled (v0.19.9)

**URL:** <https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149>\
**Category:** Elasticsearch\
**Created:** [September 26, 2012, 7:51am UTC](https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149 "2012-09-26T07:51:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Felix\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felix_2/32/2678_2.png) [@Felix\_2](https://discuss.elastic.co/u/Felix_2)\
**Post date:** [September 26, 2012, 7:51am UTC](https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149/1 "2012-09-26T07:51:49Z")

</div>

Hi,

after updating from ES v0.19.8 to v0.19.9 I get a MapperParsingException  
when percolating a document if I have \_size enabled in my mapping.

Steps to reproduce:

1. create test index  
curl -XPUT localhost:9200/test

2. update mapping  
curl -XPUT '[http://localhost:9200/test/type1/\_mapping](http://localhost:9200/test/type1/_mapping)' -d '  
{  
"type1" : {  
"\_size" : {  
"enabled" : true,  
"store" : "yes"  
}  
}  
}'

3. register percolator query:  
curl -XPUT localhost:9200/\_percolator/test/kuku -d '{  
"query" : {  
"term" : {  
"field1" : "value1"  
}  
}  
}'

4. percolate a document:  
curl -XGET localhost:9200/test/type1/\_percolate -d '{  
"doc" : {  
"field1" : "value1"  
}  
}'

This leads to the following error:

2012-09-26 09:39:21,370][DEBUG][action.percolate] [Thor Girl]  
failed to execute  
[org.elasticsearch.action.percolate.PercolateRequest@e1935d6]  
org.elasticsearch.index.mapper.MapperParsingException: Failed to parse  
[\_size]  
at  
org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:327)  
at  
org.elasticsearch.index.mapper.internal.SizeFieldMapper.postParse(SizeFieldMapper.java:122)  
at  
org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:502)  
at  
org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:438)  
at  
org.elasticsearch.index.percolator.PercolatorExecutor.percolate(PercolatorExecutor.java:257)  
at  
org.elasticsearch.index.percolator.PercolatorService.percolate(PercolatorService.java:111)  
at  
org.elasticsearch.action.percolate.TransportPercolateAction.shardOperation(TransportPercolateAction.java:93)  
at  
org.elasticsearch.action.percolate.TransportPercolateAction.shardOperation(TransportPercolateAction.java:41)  
at  
org.elasticsearch.action.support.single.custom.TransportSingleCustomOperationAction$AsyncSingleAction$2.run(TransportSingleCustomOperationAction.java:176)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)  
at  
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)  
at java.lang.Thread.run(Thread.java:680)  
Caused by: java.lang.NullPointerException  
at  
org.elasticsearch.index.mapper.internal.SizeFieldMapper.innerParseCreateField(SizeFieldMapper.java:140)  
at  
org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:171)  
at  
org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:314)  
... 11 more  
{"error":"MapperParsingException[Failed to parse [\_size]]; nested:  
","status":400}

With v0.19.8 or if you leave out step Nr. 2 all works as expected.  
Is this a known issue? Are there any workarounds for this?  
Thanks for any help.

Felix

--

---

<div class="post-metadata">

**Author:** ![Sandra\_Swagten](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandra_swagten/32/2685_2.png) [@Sandra\_Swagten](https://discuss.elastic.co/u/Sandra_Swagten)\
**Post date:** [October 15, 2012, 7:08am UTC](https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149/2 "2012-10-15T07:08:20Z")

</div>

It is fixed in 0.19.10.

---

<div class="post-metadata">

**Author:** ![Felix\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/felix_2/32/2678_2.png) [@Felix\_2](https://discuss.elastic.co/u/Felix_2)\
**Post date:** [October 18, 2012, 6:33am UTC](https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149/3 "2012-10-18T06:33:32Z")

</div>

I don't think so, I still can reproduce this issue with ES v0.9.10

Best regards  
Felix

On Monday, October 15, 2012 9:08:23 AM UTC+2, Aha Oja wrote:

> It is fixed in 0.19.10.
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/MapperParsingException-on-percolation-with-size-enabled-v0-19-9-tp4023177p4023963.html](http://elasticsearch-users.115913.n3.nabble.com/MapperParsingException-on-percolation-with-size-enabled-v0-19-9-tp4023177p4023963.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

--

---

<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:08am UTC](https://discuss.elastic.co/t/mapperparsingexception-on-percolation-with--size-enabled-v0-19-9/9149/4 "2017-07-06T03:08:12Z")

</div>

Closed on July 6, 2017, 3:08am UTC