Skip to content

Boost no longer accepted as parameter to ip mapping. #4957

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Mpdreamz opened this issue Aug 13, 2020 · 2 comments · Fixed by #4961
Closed

Boost no longer accepted as parameter to ip mapping. #4957

Mpdreamz opened this issue Aug 13, 2020 · 2 comments · Fixed by #4961

Comments

@Mpdreamz
Copy link
Member

[xUnit.net 00:04:30.6276691]     Tests.QueryDsl.Specialized.Percolate.PercolateQueryUsageTests.ReturnsExpectedResponse [SKIP]
  ! Tests.Analysis.AnalysisCrudTests.UpdateCallIsValid [1ms]
  X Tests.Mapping.Types.Specialized.Ip.IpPropertyTests.ReturnsExpectedIsValid [18ms]
  Error Message:
   Tests.Framework.EndpointTests.ResponseAssertionException : Expected response.IsValid to be True because Invalid NEST response built from a unsuccessful (400) low level call on PUT: /nest-initializer-7d25cfa0/_mapping?pretty=true&error_trace=true
# Audit trail of this API call:
 - [1] BadResponse: Node: http://localhost:9200/ Took: 00:00:00.0065626
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: PUT /nest-initializer-7d25cfa0/_mapping?pretty=true&error_trace=true. ServerError: Type: mapper_parsing_exception Reason: "unknown parameter [boost] on mapper [name] of type [ip]"
# Request:
{"properties":{"name":{"boost":1.3,"index":false,"null_value":"127.0.0.1","doc_values":true,"store":true,"type":"ip"}}}
# Response:
{
  "error" : {
    "root_cause" : [
      {
        "type" : "mapper_parsing_exception",
        "reason" : "unknown parameter [boost] on mapper [name] of type [ip]",
        "stack_trace" : "org.elasticsearch.index.mapper.MapperParsingException: unknown parameter [boost] on mapper [name] of type [ip]\n\tat org.elasticsearch.index.mapper.ParametrizedFieldMapper$Builder.parse(ParametrizedFieldMapper.java:524)\n\tat org.elasticsearch.index.mapper.ParametrizedFieldMapper$TypeParser.parse(ParametrizedFieldMapper.java:569)\n\tat o"
  },
  "status" : 400
}
@Mpdreamz
Copy link
Member Author

Another instance:

[xUnit.net 00:09:12.4484342]     Tests.Mapping.Types.Core.Keyword.KeywordPropertyTests.ReturnsExpectedIsValid [FAIL]
  X Tests.Mapping.Types.Core.Keyword.KeywordPropertyTests.ReturnsExpectedIsValid [57s 810ms]
  Error Message:
   Tests.Framework.EndpointTests.ResponseAssertionException : Expected response.IsValid to be True because Invalid NEST response built from a unsuccessful (500) low level call on PUT: /nest-fluent-10f45c92/_mapping?pretty=true&error_trace=true
# Audit trail of this API call:
 - [1] BadResponse: Node: http://localhost:9200/ Took: 00:00:00.6964628
# OriginalException: Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 500 from: PUT /nest-fluent-10f45c92/_mapping?pretty=true&error_trace=true. ServerError: Type: generation_exception Reason: "failed to serialize source for type [_doc]" CausedBy: "Type: illegal_argument_exception Reason: "cannot write xcontent for unknown value of type class org.elasticsearch.index.similarity.SimilarityProvider""
# Request:
{"properties":{"state":{"boost":1.2,"eager_global_ordinals":true,"ignore_above":50,"index":false,"index_options":"freqs","normalizer":"myCustom","norms":false,"null_value":"null","doc_values":false,"fields":{"foo":{"ignore_above":10,"type":"keyword"}},"similarity":"BM25","store":true,"type":"keyword"}}}
# Response:
{
  "error" : {
    "root_cause" : [
      {
        "type" : "generation_exception",
        "reason" : "failed to serialize source for type [_doc]",
        "stack_trace" : ""
  },
  "status" : 500
}

@russcam
Copy link
Contributor

russcam commented Aug 17, 2020

I opened #3145 to refactor mappings for 8.0.0. It may be a good opportunity now to implement this change.

russcam added a commit that referenced this issue Aug 18, 2020
This commit removes the Boost property from
Ip field mappings.

Fixes #4957
russcam added a commit that referenced this issue Aug 24, 2020
This commit removes the Boost property from
Ip field mappings.

Fixes #4957
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants