[Transform] Specify use_point_in_time in settings (#5322) (#5460)

use_point_in_time has been in the docs since before 8.18

Resolve elastic/elasticsearch#134841

(cherry picked from commit 9fe24d1)

Co-authored-by: Pat Whelan <[email protected]>

Author: github-actions[bot]

output/schema/schema.json

@@ -511,7 +511,7 @@ painless-contexts,https://www.elastic.co/docs/reference/scripting-languages/pain
 painless-execute-api,https://www.elastic.co/docs/reference/scripting-languages/painless/painless-api-examples,,
 pipeline-processor,https://www.elastic.co/docs/reference/enrich-processor/pipeline-processor,,
 pki-realm,https://www.elastic.co/docs/deploy-manage/users-roles/cluster-or-deployment-auth/pki,,
-point-in-time-api,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-open-point-in-time,https://www.elastic.co/guide/en/elasticsearch/reference/8.18/point-in-time-api.html,
+point-in-time-api,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-open-point-in-time,https://www.elastic.co/guide/en/elasticsearch/reference/8.18/point-in-time-api.html,Open a point in time API
 prevalidate-node-removal,https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-cluster,https://www.elastic.co/guide/en/elasticsearch/reference/8.18/cluster.html,
 preview-dfanalytics,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-preview-data-frame-analytics,https://www.elastic.co/guide/en/elasticsearch/reference/8.18/preview-dfanalytics.html,
 preview-transform,https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-transform-preview-transform,https://www.elastic.co/guide/en/elasticsearch/reference/8.18/preview-transform.html,

output/typescript/types.ts

@@ -130,6 +130,16 @@ export class Settings {
    * @server_default 500
    */
   max_page_search_size?: integer
+  /**
+   * Specifies whether the transform checkpoint will use the Point In Time API while searching over the source index.
+   * In general, Point In Time is an optimization that will reduce pressure on the source index by reducing the amount
+   * of refreshes and merges, but it can be expensive if a large number of Point In Times are opened and closed for a
+   * given index. The benefits and impact depend on the data being searched, the ingest rate into the source index, and
+   * the amount of other consumers searching the same source index.
+   * @ext_doc_id point-in-time-api
+   * @server_default true
+   */
+  use_point_in_time?: boolean
 
   /**
    * If `true`, the transform runs in unattended mode. In unattended mode, the transform retries indefinitely in case