# Vector Tile API: Updated mvt\_sample error

**URL:** <https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291>\
**Category:** Elasticsearch\
**Created:** [April 26, 2022, 1:17pm UTC](https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291 "2022-04-26T13:17:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joseph\_Parish](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joseph_parish/32/97848_2.png) [@Joseph\_Parish](https://discuss.elastic.co/u/Joseph_Parish)\
**Post date:** [April 26, 2022, 1:17pm UTC](https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291/1 "2022-04-26T13:17:49Z")

</div>

The latest update to the [mvt\_sample](https://github.com/thomasneirynck/mvt_sample) throws this ResponseError: x\_content\_parse\_exception: [x\_content\_parse\_exception] Reason: [1:36] [vector-tile] unknown field [grid\_agg] did you mean [grid\_type]? If the grid\_agg field is removed, the sample code works for the hits layer. Is the grid\_agg field a new component for the upcoming v8.2 geohex grid option that does not work in the current version? Also curios as to why the mvt\_sample uses the older "@elastic/Elasticsearch": "^7.15.0" client. The latest 8.1 version has many breaking changes. It would be helpful to have an example of the latest client using the geohex grid. Thanks

---

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [April 27, 2022, 12:32pm UTC](https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291/2 "2022-04-27T12:32:33Z")

</div>

Hi Joe,

[This PR](https://github.com/thomasneirynck/mvt_sample/pull/3/files) changed the demo code to work with [this change](https://github.com/elastic/elasticsearch/pull/84553) in the upcoming Elasticsearch 8.2.0 release. So the demo in the main branch is not compatible with older versions.

> Also curios as to why the mvt\_sample uses the older "@elastic/Elasticsearch": "^7.15.0" client. The latest 8.1 version has many breaking changes. It would be helpful to have an example of the latest client using the geohex grid.

Good point! I've [opened a PR](https://github.com/thomasneirynck/mvt_sample/pull/7) to update it to the latest 8.1.0 Elasticsearch client which should still work with Elasticsearch 8.2.0. But we should update the client release to 8.2.0 once it is available.

---

<div class="post-metadata">

**Author:** ![Joseph\_Parish](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joseph_parish/32/97848_2.png) [@Joseph\_Parish](https://discuss.elastic.co/u/Joseph_Parish)\
**Post date:** [May 5, 2022, 1:59am UTC](https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291/3 "2022-05-05T01:59:14Z")

</div>

thanks. great to see the hexgrid in action

---

<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:** [June 2, 2022, 1:59am UTC](https://discuss.elastic.co/t/vector-tile-api-updated-mvt-sample-error/303291/4 "2022-06-02T01:59:47Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.