OpenSearch/rest-api-spec/test/scroll/11_clear.yaml

---
"Clear scroll":
  - do:
      indices.create:
          index:  test_scroll
  - do:
      index:
          index:  test_scroll
          type:   test
          id:     42
          body:   { foo: bar }

  - do:
      indices.refresh: {}

  - do:
      search:
        index: test_scroll
        search_type: scan
        scroll: 1m
        body:
          query:
            match_all: {}

  - set: {_scroll_id: scroll_id1}

  - do:
      clear_scroll:
        scroll_id: $scroll_id1

  - do:
      catch: missing
      scroll:
        scroll_id: $scroll_id1
        
  - do:
        catch: missing
        clear_scroll:
          scroll_id: $scroll_id1
The clear scroll apis now optionally accepts a scroll_id in it body. Closes #5726 2014-04-08 20:41:32 +07:00			`---`
			`"Clear scroll":`
			`- do:`
			`indices.create:`
			`index: test_scroll`
			`- do:`
			`index:`
			`index: test_scroll`
			`type: test`
			`id: 42`
			`body: { foo: bar }`

			`- do:`
			`indices.refresh: {}`

			`- do:`
			`search:`
			`index: test_scroll`
			`search_type: scan`
			`scroll: 1m`
			`body:`
			`query:`
			`match_all: {}`

			`- set: {_scroll_id: scroll_id1}`

			`- do:`
			`clear_scroll:`
			`scroll_id: $scroll_id1`

			`- do:`
[REST] Missing scroll id now returns 404 A bad/non-existing scroll ID used to return a 200, however a 404 might be more useful. Also, this PR returns the right Exception (SearchContextMissingException) in the Java API. Additionally: Added StatusToXContent interface and RestStatusToXContentListener listener, so the appropriate RestStatus can be returned Closes #5729 2014-05-05 10:35:46 +02:00			`catch: missing`
The clear scroll apis now optionally accepts a scroll_id in it body. Closes #5726 2014-04-08 20:41:32 +07:00			`scroll:`
			`scroll_id: $scroll_id1`
Return missing (404) is a scroll_id is cleared that no longer exists. Closes #5730 2014-04-18 14:23:13 +07:00
			`- do:`
			`catch: missing`
			`clear_scroll:`
			`scroll_id: $scroll_id1`