# Elastic index option doesn't accept int4\_hnsw

**URL:** <https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961>\
**Category:** Elasticsearch\
**Tags:** vector-search\
**Created:** [November 3, 2024, 11:51am UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961 "2024-11-03T11:51:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandra\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandra_a/32/126560_2.png) [@sandra\_a](https://discuss.elastic.co/u/sandra_a)\
**Post date:** [November 3, 2024, 11:51am UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961/1 "2024-11-03T11:51:50Z")

</div>

Hi  
I want to create a dense vector index with int4\_hnsw option as said in document ([Automatically quantize vectors for kNN search](https://www.elastic.co/guide/en/elasticsearch/reference/current/dense-vector.html#dense-vector-quantization)) but after running the same example i got this error:

```json
{
  "error": {
    "root_cause": [
      {
        "type": "mapper_parsing_exception",
        "reason": "Unknown vector index options type [int4_hnsw] for field [my_vector]"
      }
    ],
    "type": "mapper_parsing_exception",
    "reason": "Failed to parse mapping: Unknown vector index options type [int4_hnsw] for field [my_vector]",
    "caused_by": {
      "type": "mapper_parsing_exception",
      "reason": "Unknown vector index options type [int4_hnsw] for field [my_vector]"
    }
  },
  "status": 400
}

```

but int8\_hnsw is acceptable!

does anybody know what should I do?

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 3, 2024, 12:45pm UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961/2 "2024-11-03T12:45:19Z")

</div>

I believe this was introduced in Elasticsearch 8.15. Are you running an older version?

---

<div class="post-metadata">

**Author:** ![sandra\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandra_a/32/126560_2.png) [@sandra\_a](https://discuss.elastic.co/u/sandra_a)\
**Post date:** [November 3, 2024, 1:38pm UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961/3 "2024-11-03T13:38:05Z")

</div>

My stack version is 8.13.1

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [November 3, 2024, 1:39pm UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961/4 "2024-11-03T13:39:43Z")

</div>

Then you need to upgrade to the latest version.

---

<div class="post-metadata">

**Author:** ![sandra\_a](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sandra_a/32/126560_2.png) [@sandra\_a](https://discuss.elastic.co/u/sandra_a)\
**Post date:** [November 3, 2024, 1:41pm UTC](https://discuss.elastic.co/t/elastic-index-option-doesnt-accept-int4-hnsw/369961/5 "2024-11-03T13:41:03Z")

</div>

Thanks a lot