OpenSearch/rest-api-spec/test/termvectors/30_realtime.yaml

---
"Realtime Term Vectors":

 - do:
      indices.create:
        index:    test_1
        body:
          settings:
            index:
              refresh_interval: -1
              number_of_replicas: 0

 - do:
      cluster.health:
          wait_for_status: green

 - do:
      index:
          index:   test_1
          type:    test
          id:      1
          body:    { foo: bar }

 - do:
      termvectors:
          index:    test_1
          type:     test
          id:       1
          realtime: 0

 - is_false: found

 - do:
      termvectors:
          index:    test_1
          type:     test
          id:       1
          realtime: 1

 - is_true: found
Term Vectors: support for realtime By default term vectors are now realtime, as opposed to previously near realtime. If they are not found in the index, they will be generated on the fly. The document is fetched from the transaction log and treated as an artificial document. One can set `realtime` parameter to `false` in order to disable this functionality. This consequently makes the MLT query realtime in fetching documents, as it previsouly used to be before switching from using the multi get API to the mtv API. Closes #7846 2014-09-23 23:21:42 +02:00			`---`
			`"Realtime Term Vectors":`

			`- do:`
			`indices.create:`
			`index: test_1`
			`body:`
			`settings:`
			`index:`
			`refresh_interval: -1`
			`number_of_replicas: 0`

			`- do:`
			`cluster.health:`
			`wait_for_status: green`

			`- do:`
			`index:`
			`index: test_1`
			`type: test`
			`id: 1`
			`body: { foo: bar }`

			`- do:`
Term Vectors: More consistent naming for term vector[s] We speak of the term vectors of a document, where each field has an associated stored term vector. Since by default we are requesting all the term vectors of a document, the HTTP request endpoint should rather be called `_termvectors` instead of `_termvector`. The usage of `_termvector` is now deprecated, as well as the transport client call to termVector and prepareTermVector. Closes #8484 2014-11-13 15:05:09 +01:00			`termvectors:`
Term Vectors: support for realtime By default term vectors are now realtime, as opposed to previously near realtime. If they are not found in the index, they will be generated on the fly. The document is fetched from the transaction log and treated as an artificial document. One can set `realtime` parameter to `false` in order to disable this functionality. This consequently makes the MLT query realtime in fetching documents, as it previsouly used to be before switching from using the multi get API to the mtv API. Closes #7846 2014-09-23 23:21:42 +02:00			`index: test_1`
			`type: test`
			`id: 1`
			`realtime: 0`

			`- is_false: found`

			`- do:`
Term Vectors: More consistent naming for term vector[s] We speak of the term vectors of a document, where each field has an associated stored term vector. Since by default we are requesting all the term vectors of a document, the HTTP request endpoint should rather be called `_termvectors` instead of `_termvector`. The usage of `_termvector` is now deprecated, as well as the transport client call to termVector and prepareTermVector. Closes #8484 2014-11-13 15:05:09 +01:00			`termvectors:`
Term Vectors: support for realtime By default term vectors are now realtime, as opposed to previously near realtime. If they are not found in the index, they will be generated on the fly. The document is fetched from the transaction log and treated as an artificial document. One can set `realtime` parameter to `false` in order to disable this functionality. This consequently makes the MLT query realtime in fetching documents, as it previsouly used to be before switching from using the multi get API to the mtv API. Closes #7846 2014-09-23 23:21:42 +02:00			`index: test_1`
			`type: test`
			`id: 1`
			`realtime: 1`

			`- is_true: found`