From 447f0995441ba71ea18cc9527b83b275979242c6 Mon Sep 17 00:00:00 2001 From: Clinton Gormley Date: Wed, 13 Apr 2016 14:29:47 +0200 Subject: [PATCH] Improve glossary to not refer to types as "like a table" (#17704) Closes #17673 --- docs/reference/glossary.asciidoc | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/reference/glossary.asciidoc b/docs/reference/glossary.asciidoc index 09fcd5b4b05..edf84f3b4c8 100644 --- a/docs/reference/glossary.asciidoc +++ b/docs/reference/glossary.asciidoc @@ -63,8 +63,9 @@ [[glossary-index]] index :: - An index is like a _database_ in a relational database. It has a - <> which defines multiple <>. + An index is like a _table_ in a relational database. It has a + <> which defines the <> in the index, + which are grouped by multiple <>. + An index is a logical namespace which maps to one or more <> and can have zero or more @@ -155,10 +156,6 @@ This allows you access to the original object directly from search results, rather than requiring a second step to retrieve the object from an ID. - + - Note: the exact JSON string that you indexed will be returned to you, - even if it contains invalid JSON. The contents of this field do not - indicate anything about how the data in the object has been indexed. [[glossary-term]] term :: @@ -182,8 +179,11 @@ [[glossary-type]] type :: - A type is like a _table_ in a relational database. Each type has a + A type represents the _type_ of document, e.g. an `email`, a `user`, or a `tweet`. + The search API can filter documents by type. + An <> can contain multiple types, and each type has a list of <> that can be specified for - <> of that type. The <> - defines how each field in the document is analyzed. + <> of that type. Fields with the same + name in different types in the same index must have the same <> + (which defines how each field in the document is indexed and made searchable).