Equivalent setting for following mapping in Elasticsearch 5.x

dadoonet · March 31, 2017, 6:41am

For now, the only way to solve that I believe is at index time or using an ingest script processor.

I opened the following issue for discussion:

github.com/elastic/elasticsearch

null_value is not supported for text fields

opened 06:40AM - 31 Mar 17 UTC

closed 03:02PM - 20 Apr 17 UTC

dadoonet

>docs help wanted :Search/Mapping

``` DELETE test PUT test { "mappings": { "my_type": { "propert…ies": { "status_code": { "type": "text", "null_value": "NULL" } } } } } ``` This is now failing in 5.x. Either it's a bug and we should still support it or we should document it as a breaking change for people who are moving their `string` mapping to `text`. Thoughts?

Topic		Replies	Views
Why null_value parameter has been removed for text field type? Elasticsearch	2	1742	April 28, 2017
Null value in field type with nested Elasticsearch	1	148	September 18, 2023
Mapping null values Elasticsearch	2	843	January 21, 2022
Null value causing errors? Elasticsearch	4	2358	July 5, 2017
Elastic search null_value for integers is failing Elasticsearch	2	3831	January 24, 2018

Equivalent setting for following mapping in Elasticsearch 5.x

Related Topics