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/update/75_ttl.yaml

93 lines
1.7 KiB
YAML
Raw Normal View History

Added tests for update()
2013-06-28 13:44:13 -04:00
---
"TTL":
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read
2013-07-01 09:58:23 -04:00
Added tests for update()
2013-06-28 13:44:13 -04:00
- do:
indices.create:
index: test_1
body:
mappings:
test:
_ttl:
enabled: 1
default: 10s
- do:
cluster.health:
wait_for_status: yellow
# blank ttl
- do:
update:
index: test_1
type: test
id: 1
body:
doc: { foo: baz }
upsert: { foo: bar }
- do:
get:
index: test_1
type: test
id: 1
fields: _ttl
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read
2013-07-01 09:58:23 -04:00
Rest: Add all meta fields to the top level json document. Some of our meta fields (such as _id, _version, ...) are returned as top-level properties of the json document, while other properties (_timestamp, _routing, ...) are returned under `fields`. This commit makes all meta fields returned as top-level properties. So eg. `GET test/test/1?fields=_timestamp,foo` would now return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "_timestamp": 10000000, "found": true, "fields": { "foo": [ "bar" ] } } ``` while it used to return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "found": true, "fields": { "_timestamp": 10000000, "foo": [ "bar" ] } } ```
2014-10-17 06:35:20 -04:00
- lte: { _ttl: 10000}
- gt: { _ttl: 0}
Added tests for update()
2013-06-28 13:44:13 -04:00
# milliseconds
- do:
update:
index: test_1
type: test
id: 1
body:
doc: { foo: baz }
upsert: { foo: bar }
add missing units to tests
2015-05-25 06:48:34 -04:00
ttl: 100000ms
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read
2013-07-01 09:58:23 -04:00
Added tests for update()
2013-06-28 13:44:13 -04:00
- do:
get:
index: test_1
type: test
id: 1
fields: _ttl
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read
2013-07-01 09:58:23 -04:00
Rest: Add all meta fields to the top level json document. Some of our meta fields (such as _id, _version, ...) are returned as top-level properties of the json document, while other properties (_timestamp, _routing, ...) are returned under `fields`. This commit makes all meta fields returned as top-level properties. So eg. `GET test/test/1?fields=_timestamp,foo` would now return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "_timestamp": 10000000, "found": true, "fields": { "foo": [ "bar" ] } } ``` while it used to return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "found": true, "fields": { "_timestamp": 10000000, "foo": [ "bar" ] } } ```
2014-10-17 06:35:20 -04:00
- lte: { _ttl: 100000}
- gt: { _ttl: 10000}
Added tests for update()
2013-06-28 13:44:13 -04:00
# duration
- do:
update:
index: test_1
type: test
id: 1
body:
doc: { foo: baz }
upsert: { foo: bar }
ttl: 20s
- do:
get:
index: test_1
type: test
id: 1
fields: _ttl
Renamed "ok" and "not_ok" to "is_true" and "is_false" and tidied up the layout to make it easier to read
2013-07-01 09:58:23 -04:00
Rest: Add all meta fields to the top level json document. Some of our meta fields (such as _id, _version, ...) are returned as top-level properties of the json document, while other properties (_timestamp, _routing, ...) are returned under `fields`. This commit makes all meta fields returned as top-level properties. So eg. `GET test/test/1?fields=_timestamp,foo` would now return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "_timestamp": 10000000, "found": true, "fields": { "foo": [ "bar" ] } } ``` while it used to return ```json { "_index": "test", "_type": "test", "_id": "1", "_version": 1, "found": true, "fields": { "_timestamp": 10000000, "foo": [ "bar" ] } } ```
2014-10-17 06:35:20 -04:00
- lte: { _ttl: 20000}
- gt: { _ttl: 10000}
Added tests for update()
2013-06-28 13:44:13 -04:00
# with timestamp
- do:
[REST] Render REST errors in a structural way This commit adds support for structural errors / failures / exceptions on the elasticsearch REST layer. Exceptions are rendering with at least a `type` and a `reason` corresponding to the exception name and the message. Some expcetions like the ones associated with an index or a shard will have additional information about the index the exception was triggered on or the shard respectivly. Each rendered response will also contain a list of root causes which is a list of distinct shard level errors returned for the request. Root causes are the lowest level elasticsearch exception found per shard response and are intended to be displayed to the user to indicate the soruce of the exception. Shard level response are by-default grouped by their type and reason to reduce the amount of duplicates retunred. Yet, the same exception retunred from different indices will not be grouped. Closes #3303
2015-04-24 03:36:10 -04:00
catch: /already_expired_exception/
Added tests for update()
2013-06-28 13:44:13 -04:00
index:
index: test_1
type: test
id: 1
body: { foo: bar }
ttl: 20s
timestamp: 2013-06-23T18:14:40