honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/rest-api-spec/test/indices.put_mapping/10_basic.yaml

63 lines
1.8 KiB
YAML
Raw Normal View History

Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
---
"Test Create and update mapping":
- do:
indices.create:
index: test_index
- do:
indices.put_mapping:
index: test_index
type: test_type
body:
test_type:
properties:
Replaced the multi-field type in favour for the multi fields option that can be set on any core field. When upgrading to ES 1.0 the existing mappings with a multi-field type automatically get replaced to a core field with the new `fields` option. If a `multi_field` type-ed field doesn't have a main / default field, a default field will be chosen for the multi fields syntax. The new main field type will be equal to the first `multi_field` fields' field or type string if no fields have been configured for the `multi_field` field and in both cases the default index will not be indexed (`index=no` is set on the default field). If a `multi_field` typed field has a default field, that field will replace the `multi_field` typed field. Closes to #4521
2013-12-27 20:05:31 -05:00
text1:
type: string
analyzer: whitespace
text2:
Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
type: string
analyzer: whitespace
- do:
indices.get_mapping:
index: test_index
[Test] Revert temporary fixes for update mapping on recovery issue This reverts: "Test: Temporarily change delete/put_mapping to wait for green": commit e408f8f638c2dd97a3ec86c8a9ac940f43ab37a0. "[TEST] wait for green to update mapping": commit b3641a2ee6eb23318d49f5f04b39149e70c2b65b.
2014-07-07 16:17:07 -04:00
Consistent REST API changes for GETting data * Made GET mappings consistent, supporting * /{index}/_mappings/{type} * /{index}/_mapping/{type} * /_mapping/{type} * Added "mappings" in the JSON response to align it with other responses * Made GET warmers consistent, support /{index}/_warmers/{type} and /_warmer, /_warner/{name} as well as wildcards and _all notation * Made GET aliases consistent, support /{index}/_aliases/{name} and /_alias, /_aliases/{name} as well as wildcards and _all notation * Made GET settings consistent, added /{index}/_setting/{name}, /_settings/{name} as well as supportings wildcards in settings name * Returning empty JSON instead of a 404, if a specific warmer/ setting/alias/type is missing * Added a ton of spec tests for all of the above * Added a couple of more integration tests for several features Relates #4071
2014-01-14 16:31:42 -05:00
- match: {test_index.mappings.test_type.properties.text1.type: string}
- match: {test_index.mappings.test_type.properties.text1.analyzer: whitespace}
- match: {test_index.mappings.test_type.properties.text2.type: string}
- match: {test_index.mappings.test_type.properties.text2.analyzer: whitespace}
Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
- do:
indices.put_mapping:
index: test_index
type: test_type
body:
test_type:
properties:
Replaced the multi-field type in favour for the multi fields option that can be set on any core field. When upgrading to ES 1.0 the existing mappings with a multi-field type automatically get replaced to a core field with the new `fields` option. If a `multi_field` type-ed field doesn't have a main / default field, a default field will be chosen for the multi fields syntax. The new main field type will be equal to the first `multi_field` fields' field or type string if no fields have been configured for the `multi_field` field and in both cases the default index will not be indexed (`index=no` is set on the default field). If a `multi_field` typed field has a default field, that field will replace the `multi_field` typed field. Closes to #4521
2013-12-27 20:05:31 -05:00
text1:
Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
type: multi_field
fields:
Replaced the multi-field type in favour for the multi fields option that can be set on any core field. When upgrading to ES 1.0 the existing mappings with a multi-field type automatically get replaced to a core field with the new `fields` option. If a `multi_field` type-ed field doesn't have a main / default field, a default field will be chosen for the multi fields syntax. The new main field type will be equal to the first `multi_field` fields' field or type string if no fields have been configured for the `multi_field` field and in both cases the default index will not be indexed (`index=no` is set on the default field). If a `multi_field` typed field has a default field, that field will replace the `multi_field` typed field. Closes to #4521
2013-12-27 20:05:31 -05:00
text1:
Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
type: string
analyzer: whitespace
text_raw:
type: string
index: not_analyzed
Replaced the multi-field type in favour for the multi fields option that can be set on any core field. When upgrading to ES 1.0 the existing mappings with a multi-field type automatically get replaced to a core field with the new `fields` option. If a `multi_field` type-ed field doesn't have a main / default field, a default field will be chosen for the multi fields syntax. The new main field type will be equal to the first `multi_field` fields' field or type string if no fields have been configured for the `multi_field` field and in both cases the default index will not be indexed (`index=no` is set on the default field). If a `multi_field` typed field has a default field, that field will replace the `multi_field` typed field. Closes to #4521
2013-12-27 20:05:31 -05:00
text2:
type: string
analyzer: whitespace
fields:
text_raw:
type: string
index: not_analyzed
Add basic tests for put mapping
2013-07-15 08:43:27 -04:00
- do:
indices.get_mapping:
index: test_index
[Test] Revert temporary fixes for update mapping on recovery issue This reverts: "Test: Temporarily change delete/put_mapping to wait for green": commit e408f8f638c2dd97a3ec86c8a9ac940f43ab37a0. "[TEST] wait for green to update mapping": commit b3641a2ee6eb23318d49f5f04b39149e70c2b65b.
2014-07-07 16:17:07 -04:00
Consistent REST API changes for GETting data * Made GET mappings consistent, supporting * /{index}/_mappings/{type} * /{index}/_mapping/{type} * /_mapping/{type} * Added "mappings" in the JSON response to align it with other responses * Made GET warmers consistent, support /{index}/_warmers/{type} and /_warmer, /_warner/{name} as well as wildcards and _all notation * Made GET aliases consistent, support /{index}/_aliases/{name} and /_alias, /_aliases/{name} as well as wildcards and _all notation * Made GET settings consistent, added /{index}/_setting/{name}, /_settings/{name} as well as supportings wildcards in settings name * Returning empty JSON instead of a 404, if a specific warmer/ setting/alias/type is missing * Added a ton of spec tests for all of the above * Added a couple of more integration tests for several features Relates #4071
2014-01-14 16:31:42 -05:00
- match: {test_index.mappings.test_type.properties.text1.type: string}
- match: {test_index.mappings.test_type.properties.text1.fields.text_raw.index: not_analyzed}
- match: {test_index.mappings.test_type.properties.text2.type: string}
- match: {test_index.mappings.test_type.properties.text2.fields.text_raw.index: not_analyzed}