@@ -113,7 +113,7 @@ In the delete phase, an index is no longer needed and can safely be deleted.
113
113
114
114
A document is a JSON document which is stored in Elasticsearch. It is
115
115
like a row in a table in a relational database. Each document is
116
- stored in an <<glossary-index,index>> and has a <<glossary- type,type>> and an
116
+ stored in an <<glossary-index,index>> and has a type and an
117
117
<<glossary-id,id>>.
118
118
+
119
119
A document is a JSON object (also known in other languages as a hash /
@@ -140,7 +140,7 @@ date), or a nested structure like an array or an object. A field is
140
140
similar to a column in a table in a relational database.
141
141
+
142
142
The <<glossary-mapping,mapping>> for each field has a field _type_ (not to
143
- be confused with document <<glossary- type,type>> ) which indicates the type
143
+ be confused with document type) which indicates the type
144
144
of data that can be stored in that field, eg `integer`, `string`,
145
145
`object`. The mapping also allows you to define (amongst other things)
146
146
how the value for a field should be analyzed.
@@ -324,7 +324,7 @@ The cluster that pulls data from a <<glossary-remote-cluster,remote cluster>> in
324
324
[[glossary-mapping]] mapping ::
325
325
326
326
A mapping is like a _schema definition_ in a relational database. Each
327
- <<glossary-index,index>> has a mapping, which defines a <<glossary- type,type>> ,
327
+ <<glossary-index,index>> has a mapping, which defines a type,
328
328
plus a number of index-wide settings.
329
329
+
330
330
A mapping can either be defined explicitly, or it will be generated
0 commit comments