put-transform.asciidoc 4.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164
  1. [role="xpack"]
  2. [testenv="basic"]
  3. [[put-data-frame-transform]]
  4. === Create {dataframe-transforms} API
  5. [subs="attributes"]
  6. ++++
  7. <titleabbrev>Create {dataframe-transforms}</titleabbrev>
  8. ++++
  9. Instantiates a {dataframe-transform}.
  10. beta[]
  11. [[put-data-frame-transform-request]]
  12. ==== {api-request-title}
  13. `PUT _data_frame/transforms/<data_frame_transform_id>`
  14. [[put-data-frame-transform-prereqs]]
  15. ==== {api-prereq-title}
  16. * If the {es} {security-features} are enabled, you must have
  17. `manage_data_frame_transforms` cluster privileges to use this API. The built-in
  18. `data_frame_transforms_admin` role has these privileges. You must also
  19. have `read` and `view_index_metadata` privileges on the source index and `read`,
  20. `create_index`, and `index` privileges on the destination index. For more
  21. information, see {stack-ov}/security-privileges.html[Security privileges] and
  22. {stack-ov}/built-in-roles.html[Built-in roles].
  23. [[put-data-frame-transform-desc]]
  24. ==== {api-description-title}
  25. IMPORTANT: You must use {kib} or this API to create a {dataframe-transform}.
  26. Do not put a {dataframe-transform} directly into any
  27. `.data-frame-internal*` indices using the Elasticsearch index API.
  28. If {es} {security-features} are enabled, do not give users any
  29. privileges on `.data-frame-internal*` indices.
  30. [[put-data-frame-transform-path-parms]]
  31. ==== {api-path-parms-title}
  32. `<data_frame_transform_id>`::
  33. (Required, string) Identifier for the {dataframe-transform}. This identifier
  34. can contain lowercase alphanumeric characters (a-z and 0-9), hyphens, and
  35. underscores. It must start and end with alphanumeric characters.
  36. [[put-data-frame-transform-request-body]]
  37. ==== {api-request-body-title}
  38. `description`::
  39. (Optional, string) Free text description of the {dataframe-transform}.
  40. `dest`::
  41. (Required, object) Required. The destination configuration, which has the
  42. following properties:
  43. `index`:::
  44. (Required, string) The _destination index_ for the {dataframe-transform}.
  45. `pipeline`:::
  46. (Optional, string) The unique identifier for a <<pipeline,pipeline>>.
  47. `frequency`::
  48. (Optional, time units) The interval between checks for changes in the source indices
  49. when the {dataframe-transform} is running continuously. Defaults to `1m`.
  50. The lowest permitted value is `1s`; the highest `1h`.
  51. `pivot`::
  52. (Required, object) Defines the pivot function `group by` fields and the aggregation to
  53. reduce the data. See <<data-frame-transform-pivot>>.
  54. `source`::
  55. (Required, object) The source configuration, which has the following
  56. properties:
  57. `index`:::
  58. (Required, string or array) The _source indices_ for the
  59. {dataframe-transform}. It can be a single index, an index pattern (for
  60. example, `"myindex*"`), or an array of indices (for example,
  61. `["index1", "index2"]`).
  62. `query`:::
  63. (Optional, object) A query clause that retrieves a subset of data from the
  64. source index. See <<query-dsl>>.
  65. `sync`::
  66. (Optional, object) Defines the properties required to run continuously.
  67. `time`:::
  68. (Required, object) Specifies that the {dataframe-transform} uses a time
  69. field to synchronize the source and destination indices.
  70. `field`::::
  71. (Required, string) The date field that is used to identify new documents
  72. in the source.
  73. +
  74. --
  75. TIP: In general, it’s a good idea to use a field that contains the
  76. <<accessing-ingest-metadata,ingest timestamp>>. If you use a different field,
  77. you might need to set the `delay` such that it accounts for data transmission
  78. delays.
  79. --
  80. `delay`::::
  81. (Optional, time units) The time delay between the current time and the
  82. latest input data time. The default value is `60s`.
  83. [[put-data-frame-transform-example]]
  84. ==== {api-examples-title}
  85. [source,js]
  86. --------------------------------------------------
  87. PUT _data_frame/transforms/ecommerce_transform
  88. {
  89. "source": {
  90. "index": "kibana_sample_data_ecommerce",
  91. "query": {
  92. "term": {
  93. "geoip.continent_name": {
  94. "value": "Asia"
  95. }
  96. }
  97. }
  98. },
  99. "pivot": {
  100. "group_by": {
  101. "customer_id": {
  102. "terms": {
  103. "field": "customer_id"
  104. }
  105. }
  106. },
  107. "aggregations": {
  108. "max_price": {
  109. "max": {
  110. "field": "taxful_total_price"
  111. }
  112. }
  113. }
  114. },
  115. "description": "Maximum priced ecommerce data by customer_id in Asia",
  116. "dest": {
  117. "index": "kibana_sample_data_ecommerce_transform",
  118. "pipeline": "add_timestamp_pipeline"
  119. },
  120. "frequency": "5m",
  121. "sync": {
  122. "time": {
  123. "field": "order_date",
  124. "delay": "60s"
  125. }
  126. }
  127. }
  128. --------------------------------------------------
  129. // CONSOLE
  130. // TEST[setup:kibana_sample_data_ecommerce]
  131. When the transform is created, you receive the following results:
  132. [source,js]
  133. ----
  134. {
  135. "acknowledged" : true
  136. }
  137. ----
  138. // TESTRESPONSE