honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/mapping/params.asciidoc

83 lines
1.9 KiB
Plaintext
Raw Normal View History

Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
[[mapping-params]]
== Mapping parameters
The following pages provide detailed explanations of the various mapping
parameters that are used by <<mapping-types,field mappings>>:
The following mapping parameters are common to some or all field datatypes:
* <<analyzer,`analyzer`>>
Add the ability to set an analyzer on keyword fields. (#21919) This adds a new `normalizer` property to `keyword` fields that pre-processes the field value prior to indexing, but without altering the `_source`. Note that only the normalization components that work on a per-character basis are applied, so for instance stemming filters will be ignored while lowercasing or ascii folding will be applied. Closes #18064
2016-12-30 03:36:10 -05:00
* <<normalizer, `normalizer`>>
Change the field mapping index time boost into a query time boost. Index time boost will still be applied for indices created before 5.0.0.
2016-03-02 04:51:47 -05:00
* <<mapping-boost,`boost`>>
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
* <<coerce,`coerce`>>
* <<copy-to,`copy_to`>>
* <<doc-values,`doc_values`>>
* <<dynamic,`dynamic`>>
* <<enabled,`enabled`>>
* <<fielddata,`fielddata`>>
Reorganize docs of global ordinals. (#24982) Currently global ordinals are documented under `fielddata`. It moves them to their own file since they also work with doc values and fielddata is on the way out. Closes #23101
2017-06-01 10:47:44 -04:00
* <<eager-global-ordinals,`eager_global_ordinals`>>
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
* <<mapping-date-format,`format`>>
* <<ignore-above,`ignore_above`>>
* <<ignore-malformed,`ignore_malformed`>>
* <<index-options,`index_options`>>
* <<mapping-index,`index`>>
* <<multi-fields,`fields`>>
* <<norms,`norms`>>
* <<null-value,`null_value`>>
The name "position_offset_gap" is confusing because Lucene has three similar sounding things: * Analyzer#getPositionIncrementGap * Analyzer#getOffsetGap * IndexOptions.DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS and * FieldType#storeTermVectorOffsets Rename position_offset_gap to position_increment_gap closes #13056
2015-08-22 04:39:18 -04:00
* <<position-increment-gap,`position_increment_gap`>>
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
* <<properties,`properties`>>
* <<search-analyzer,`search_analyzer`>>
* <<similarity,`similarity`>>
* <<mapping-store,`store`>>
* <<term-vector,`term_vector`>>
include::params/analyzer.asciidoc[]
Add the ability to set an analyzer on keyword fields. (#21919) This adds a new `normalizer` property to `keyword` fields that pre-processes the field value prior to indexing, but without altering the `_source`. Note that only the normalization components that work on a per-character basis are applied, so for instance stemming filters will be ignored while lowercasing or ascii folding will be applied. Closes #18064
2016-12-30 03:36:10 -05:00
include::params/normalizer.asciidoc[]
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
include::params/boost.asciidoc[]
include::params/coerce.asciidoc[]
include::params/copy-to.asciidoc[]
include::params/doc-values.asciidoc[]
include::params/dynamic.asciidoc[]
include::params/enabled.asciidoc[]
Reorganize docs of global ordinals. (#24982) Currently global ordinals are documented under `fielddata`. It moves them to their own file since they also work with doc values and fielddata is on the way out. Closes #23101
2017-06-01 10:47:44 -04:00
include::params/eager-global-ordinals.asciidoc[]
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
include::params/fielddata.asciidoc[]
include::params/format.asciidoc[]
include::params/ignore-above.asciidoc[]
include::params/ignore-malformed.asciidoc[]
include::params/index.asciidoc[]
include::params/index-options.asciidoc[]
include::params/multi-fields.asciidoc[]
include::params/norms.asciidoc[]
include::params/null-value.asciidoc[]
The name "position_offset_gap" is confusing because Lucene has three similar sounding things: * Analyzer#getPositionIncrementGap * Analyzer#getOffsetGap * IndexOptions.DOCS_AND_FREQS_AND_POSITIONS_AND_OFFSETS and * FieldType#storeTermVectorOffsets Rename position_offset_gap to position_increment_gap closes #13056
2015-08-22 04:39:18 -04:00
include::params/position-increment-gap.asciidoc[]
Docs: Mapping docs completely rewritten for 2.0
2015-08-06 11:24:29 -04:00
include::params/properties.asciidoc[]
include::params/search-analyzer.asciidoc[]
include::params/similarity.asciidoc[]
include::params/store.asciidoc[]
include::params/term-vector.asciidoc[]