honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Updated the breaking changes for the fields param 

Closes #4888
This commit is contained in:
Clinton Gormley 2014-01-25 12:34:15 +01:00
parent 9a37922e57
commit 1aa1e83e03
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/reference/migration/migrate_1_0.asciidoc
View File

@ -311,6 +311,13 @@ by disabling wildcard expansion on destructive actions.
code. The only exception to this rule is when `fields` is used to retrieve code. The only exception to this rule is when `fields` is used to retrieve
metadata like the `routing` value, which are always singular. Metadata metadata like the `routing` value, which are always singular. Metadata
fields are always returned as scalars. fields are always returned as scalars.
+
The `fields` parameter is intended to be used for retrieving stored fields,
rather than for fields extracted from the `_source`. That means that it can no
longer be used to return whole objects and it no longer accepts the
`_source.fieldname` format. For these you should use the
<<search-request-source-filtering,`_source`&#32; `_source_include` and `_source_exclude`>>
parameters instead.
* Settings, like `index.analysis.analyzer.default` are now returned as proper * Settings, like `index.analysis.analyzer.default` are now returned as proper
nested JSON objects, which makes them easier to work with programatically: nested JSON objects, which makes them easier to work with programatically: