Cannot be parsed to boolean windows versus linux


(Scott Fauerbach) #1

I have a BRAND NEW install of 5.3.0 on Windows, an older version(2.3.2) on Ubuntu 16.04
When I tried to PUT {"settings": {"mapper": {"dynamic": "strict"}}} at localhost:9200/test I get this:

{
	"error": {
		"root_cause": [{
			"type": "illegal_argument_exception",
			"reason": "Failed to parse value [strict] cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]"
		}],
		"type": "illegal_argument_exception",
		"reason": "Failed to parse value [strict] cannot be parsed to boolean [ true/1/on/yes OR false/0/off/no ]"
	},
	"status": 400
}

But it works on 2.3.2

Any ideas on why this doesn't work anymore?


(Mark Walkom) #2

What does the entire request look like?


(Scott Fauerbach) #3

curl -XPUT 'http://localhost:9200/test' -d'{"settings": {"mapper": {"dynamic": "strict"}}}'

I'm almost certain it's a version thing, as I mentioned against 5.3 it fails, against 2.3.2 works

I think mapper is deprecated in v5


(system) #4

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