123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222 |
- [[indices-get-field-mapping]]
- === Get field mapping API
- ++++
- <titleabbrev>Get field mapping</titleabbrev>
- ++++
- Retrieves <<mapping,mapping definitions>> for one or more fields. This is useful
- if you don't need the <<indices-get-mapping,complete mapping>> of an index or
- your index contains a large number of fields.
- [source,js]
- ----
- GET /twitter/_mapping/field/user
- ----
- // CONSOLE
- // TEST[setup:twitter]
- [[get-field-mapping-api-request]]
- ==== {api-request-title}
- `GET /_mapping/field/<field>`
- `GET /<index>/_mapping/field/<field>`
- [[get-field-mapping-api-path-params]]
- ==== {api-path-parms-title}
- include::{docdir}/rest-api/common-parms.asciidoc[tag=index]
- `<field>`::
- (Optional, string) Comma-separated list or wildcard expression of fields used to
- limit returned information.
- [[get-field-mapping-api-query-params]]
- ==== {api-query-parms-title}
- include::{docdir}/rest-api/common-parms.asciidoc[tag=allow-no-indices]
- include::{docdir}/rest-api/common-parms.asciidoc[tag=expand-wildcards]
- include::{docdir}/rest-api/common-parms.asciidoc[tag=include-type-name]
- include::{docdir}/rest-api/common-parms.asciidoc[tag=index-ignore-unavailable]
- `include_defaults`::
- (Optional, boolean) If `true`, the response includes default mapping values.
- Defaults to `false`.
- include::{docdir}/rest-api/common-parms.asciidoc[tag=local]
- [[get-field-mapping-api-example]]
- ==== {api-examples-title}
- [[get-field-mapping-api-basic-ex]]
- ===== Example with index setup
- You can provide field mappings when creating a new index. The following
- <<indices-create-index, create index>> API request creates the `publications`
- index with several field mappings.
- [source,js]
- --------------------------------------------------
- PUT /publications
- {
- "mappings": {
- "properties": {
- "id": { "type": "text" },
- "title": { "type": "text"},
- "abstract": { "type": "text"},
- "author": {
- "properties": {
- "id": { "type": "text" },
- "name": { "type": "text" }
- }
- }
- }
- }
- }
- --------------------------------------------------
- // CONSOLE
- The following returns the mapping of the field `title` only:
- [source,js]
- --------------------------------------------------
- GET publications/_mapping/field/title
- --------------------------------------------------
- // CONSOLE
- // TEST[continued]
- The API returns the following response:
- [source,console-result]
- --------------------------------------------------
- {
- "publications": {
- "mappings": {
- "title": {
- "full_name": "title",
- "mapping": {
- "title": {
- "type": "text"
- }
- }
- }
- }
- }
- }
- --------------------------------------------------
- [[get-field-mapping-api-specific-fields-ex]]
- ===== Specifying fields
- The get mapping api allows you to specify a comma-separated list of fields.
- For instance to select the `id` of the `author` field, you must use its full name `author.id`.
- [source,js]
- --------------------------------------------------
- GET publications/_mapping/field/author.id,abstract,name
- --------------------------------------------------
- // CONSOLE
- // TEST[continued]
- returns:
- [source,console-result]
- --------------------------------------------------
- {
- "publications": {
- "mappings": {
- "author.id": {
- "full_name": "author.id",
- "mapping": {
- "id": {
- "type": "text"
- }
- }
- },
- "abstract": {
- "full_name": "abstract",
- "mapping": {
- "abstract": {
- "type": "text"
- }
- }
- }
- }
- }
- }
- --------------------------------------------------
- The get field mapping API also supports wildcard notation.
- [source,js]
- --------------------------------------------------
- GET publications/_mapping/field/a*
- --------------------------------------------------
- // CONSOLE
- // TEST[continued]
- returns:
- [source,console-result]
- --------------------------------------------------
- {
- "publications": {
- "mappings": {
- "author.name": {
- "full_name": "author.name",
- "mapping": {
- "name": {
- "type": "text"
- }
- }
- },
- "abstract": {
- "full_name": "abstract",
- "mapping": {
- "abstract": {
- "type": "text"
- }
- }
- },
- "author.id": {
- "full_name": "author.id",
- "mapping": {
- "id": {
- "type": "text"
- }
- }
- }
- }
- }
- }
- --------------------------------------------------
- [[get-field-mapping-api-multi-index-ex]]
- ===== Multiple indices and fields
- The get field mapping API can be used to get the mapping of multiple fields from more than one index
- with a single call. General usage of the API follows the
- following syntax: `host:port/<index>/_mapping/field/<field>` where
- `<index>` and `<field>` can stand for comma-separated list of names or wild cards. To
- get mappings for all indices you can use `_all` for `<index>`. The
- following are some examples:
- [source,js]
- --------------------------------------------------
- GET /twitter,kimchy/_mapping/field/message
- GET /_all/_mapping/field/message,user.id
- GET /_all/_mapping/field/*.id
- --------------------------------------------------
- // CONSOLE
- // TEST[setup:twitter]
- // TEST[s/^/PUT kimchy\nPUT book\n/]
|