OpenSearch/docs/reference/migration/migrate_6_0/search.asciidoc

[[breaking_60_search_changes]]
=== Search and Query DSL changes

==== Changes to queries

* The `collect_payloads` parameter of the `span_near` query has been removed. Payloads will be
  loaded when needed.

* Queries on boolean fields now strictly parse boolean-like values. This means
  only the strings `"true"` and `"false"` will be parsed into their boolean
  counterparts. Other strings will cause an error to be thrown.


==== Search shards API

The search shards API no longer accepts the `type` url parameter, which didn't
have any effect in previous versions.
Remove collect payloads parameter The collect_payloads parameter of the span_near query was previously deprecated with the intention to be removed. This commit removes this parameter. Relates #20385 2016-09-08 09:37:36 -04:00			`[[breaking_60_search_changes]]`
			`=== Search and Query DSL changes`

			`==== Changes to queries`

			* The `collect_payloads` parameter of the `span_near` query has been removed. Payloads will be
			`loaded when needed.`
Be strict when parsing values searching for booleans (#21555) This changes only the query parsing behavior to be strict when searching on boolean values. We continue to accept the variety of values during index time, but searches will only be parsed using `"true"` or `"false"`. Resolves #21545 2016-11-15 10:36:57 -07:00
			`* Queries on boolean fields now strictly parse boolean-like values. This means`
			only the strings `"true"` and `"false"` will be parsed into their boolean
			`counterparts. Other strings will cause an error to be thrown.`
Remove ignored type parameter in search_shards api (#21688) The `type` parameter has always been accepted by the search_shards api, probably to make the api and its urls the same as search. Truth is that the type never had any effect, it's been ignored from day one while accepting it may make users think that we actually do something with it. This commit removes support for the type parameter from the REST layer and the Java API. Backwards compatibility is maintained on the transport layer though. The new added serialization test also uncovered a bug in the java API where the `ClusterSearchShardsRequest` could be created with no arguments, but the indices were required to be not null otherwise the request couldn't be serialized as `writeTo` would throw NPE. Fixed by setting a default value (empty array) for indices. 2016-11-22 17:22:33 +01:00

			`==== Search shards API`

			The search shards API no longer accepts the `type` url parameter, which didn't
			`have any effect in previous versions.`