summaryrefslogtreecommitdiff
path: root/docs/reference/mapping/types.asciidoc
diff options
context:
space:
mode:
authorClinton Gormley <clint@traveljury.com>2015-08-06 20:09:42 +0200
committerClinton Gormley <clint@traveljury.com>2015-08-06 20:09:42 +0200
commit9da8822aedcc01b4f44551947136b0f38425e2c5 (patch)
tree6ed5dd4b9c7c612eb87e0dd20373383e368a0152 /docs/reference/mapping/types.asciidoc
parent00093a21dccf9599e28d18c20b6824c5a47ff90d (diff)
Docs: Made multi-fields more prominent
Diffstat (limited to 'docs/reference/mapping/types.asciidoc')
-rw-r--r--docs/reference/mapping/types.asciidoc14
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/reference/mapping/types.asciidoc b/docs/reference/mapping/types.asciidoc
index f7c93b0471..abefda4208 100644
--- a/docs/reference/mapping/types.asciidoc
+++ b/docs/reference/mapping/types.asciidoc
@@ -40,6 +40,20 @@ Attachment datatype::
which supports indexing ``attachments'' like Microsoft Office formats, Open
Document formats, ePub, HTML, etc. into an `attachment` datatype.
+[float]
+=== Multi-fields
+
+It is often useful to index the same field in different ways for different
+purposes. For instance, a `string` field could be <<mapping-index,indexed>> as
+an `analyzed` field for full-text search, and as a `not_analyzed` field for
+sorting or aggregations. Alternatively, you could index a string field with
+the <<analysis-standard-analyzer,`standard` analyzer>>, the
+<<english-analyzer,`english`>> analyzer, and the
+<<french-analyzer,`french` analyzer>>.
+
+This is the purpose of _multi-fields_. Most datatypes support multi-fields
+via the <<multi-fields>> parameter.
+
include::types/array.asciidoc[]
include::types/binary.asciidoc[]