95be11f6fb
There has been some confusion over the definition of a field type family. This PR clarifies the definition in the docs: the two types should have the exact same search behavior (including supporting the same queries/ aggs, and producing the same response). It's not sufficient for them to just support the samme search operations. This change also fixes an inaccurate statement that there is only one field type family so far. |
||
|---|---|---|
| .. | ||
| dynamic | ||
| fields | ||
| params | ||
| types | ||
| dynamic-mapping.asciidoc | ||
| explicit-mapping.asciidoc | ||
| fields.asciidoc | ||
| mapping-settings-limit.asciidoc | ||
| params.asciidoc | ||
| removal_of_types.asciidoc | ||
| runtime.asciidoc | ||
| types.asciidoc | ||