# Indexing geo\_shape in 2.0.0-rc1 (BUG?)

**URL:** <https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447>\
**Category:** Elasticsearch\
**Created:** [October 18, 2015, 3:52pm UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447 "2015-10-18T15:52:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![michel-kraemer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michel-kraemer/32/5326_2.png) [@michel-kraemer](https://discuss.elastic.co/u/michel-kraemer)\
**Post date:** [October 18, 2015, 3:52pm UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/1 "2015-10-18T15:52:50Z")

</div>

I'm using the following requests to index a document with a geo\_shape:

```
curl -X PUT http://localhost:9200/test/

curl -X PUT http://localhost:9200/test/_mapping/object -d '
{
    "object" : {
        "properties" : {
            "bbox" : {
                "type": "geo_shape",
                "precision": "1cm"
            }
        }
    }
}'

curl -X POST http://localhost:9200/test/object -d '
{
    "bbox" : {
        "type" : "envelope",
        "coordinates" : [[-45.0, 45.0], [45.0, -45.0] ]
    }
}'

```

Under 1.7.2 this works flawlessly and everything is done within a couple of milliseconds. But with 2.0.0-rc1 the last POST request takes several seconds and then crashes with an OutOfMemoryError (Java Heap Space).

Is this a bug or am I doing something wrong?

Cheers,  
Michel

---

<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:** [October 18, 2015, 9:17pm UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/2 "2015-10-18T21:17:30Z")

</div>

Looks like a bug to me!

I've raised [this](https://github.com/elastic/elasticsearch/issues/14181) on GH, thanks heaps for reporting it!

---

<div class="post-metadata">

**Author:** ![michel-kraemer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michel-kraemer/32/5326_2.png) [@michel-kraemer](https://discuss.elastic.co/u/michel-kraemer)\
**Post date:** [October 19, 2015, 4:57am UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/3 "2015-10-19T04:57:20Z")

</div>

Thanks a lot, Mark!

---

<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:** [October 20, 2015, 10:34pm UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/4 "2015-10-20T22:34:12Z")

</div>

As was pointed out in the GH issue (and I totally missed this originally), you're using a resolution of 1cm, so you have to expect that to use a lot of heap.

---

<div class="post-metadata">

**Author:** ![michel-kraemer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michel-kraemer/32/5326_2.png) [@michel-kraemer](https://discuss.elastic.co/u/michel-kraemer)\
**Post date:** [October 21, 2015, 4:45am UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/5 "2015-10-21T04:45:36Z")

</div>

Thanks. I replied on GitHub.

Michel

---

<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 5, 2017, 11:43pm UTC](https://discuss.elastic.co/t/indexing-geo-shape-in-2-0-0-rc1-bug/32447/6 "2017-07-05T23:43:42Z")

</div>