Elasticsearch: 7.10 no longer accepts boost mapping on some properties

Created on 12 Nov 2020  路  5Comments  路  Source: elastic/elasticsearch

PUT /index-a


PUT /index-a/_mapping
{"properties":{"numberOfCommits":{"boost":1.5,"coerce":true,"ignore_malformed":true,"index":false,"null_value":0.0,"doc_values":true,"similarity":"BM25","store":true,"type":"integer"}}}

on 7.9.0 returns:

{
  "acknowledged" : true
}

In 7.10.0

{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "unknown parameter [boost] on mapper [numberOfCommits] of type [integer]"
      }
    ],
    "type" : "mapper_parsing_exception",
    "reason" : "unknown parameter [boost] on mapper [numberOfCommits] of type [integer]"
  },
  "status" : 400
}

This happens for all number type mappings, ip and token_count property mappings.

:SearcSearch >breaking >bug Search

Most helpful comment

This is definitely an error, you should get a deprecation message but not an error

All 5 comments

Pinging @elastic/es-search (:Search/Search)

In 7.10 boost is still accepted on text and keyword fields, but is no longer accepted on numeric types

This is definitely an error, you should get a deprecation message but not an error

Fixed by #64999

Was this page helpful?
0 / 5 - 0 ratings