-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[DOCS] Adds sync to data frame transform API #44254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
+32
−6
Merged
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -67,6 +67,15 @@ IMPORTANT: You must use {kib} or this API to create a {dataframe-transform}. | |
`source`:: | ||
(object) Required. The source configuration, which consists of `index` and | ||
optionally a `query`. See <<data-frame-transform-source>>. | ||
|
||
`sync`:: | ||
(Optional, object) Defines the properties required to run continuously. | ||
`field`::: | ||
(Required, string) The date field that is used to identify new documents in | ||
the source. | ||
`delay`::: | ||
(Optional, time units) The time delay between the current time and the | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we identified yesterday that we need a default value for delay, I will update this comment once we agreed on a value. |
||
latest input data time. | ||
|
||
[[put-data-frame-transform-example]] | ||
==== {api-examples-title} | ||
|
@@ -85,11 +94,6 @@ PUT _data_frame/transforms/ecommerce_transform | |
} | ||
} | ||
}, | ||
"dest": { | ||
"index": "kibana_sample_data_ecommerce_transform", | ||
"pipeline": "add_timestamp_pipeline" | ||
}, | ||
"frequency": "5m", | ||
"pivot": { | ||
"group_by": { | ||
"customer_id": { | ||
|
@@ -106,7 +110,18 @@ PUT _data_frame/transforms/ecommerce_transform | |
} | ||
} | ||
}, | ||
"description": "Maximum priced ecommerce data by customer_id in Asia" | ||
"description": "Maximum priced ecommerce data by customer_id in Asia", | ||
"dest": { | ||
"index": "kibana_sample_data_ecommerce_transform", | ||
"pipeline": "add_timestamp_pipeline" | ||
}, | ||
"frequency": "5m", | ||
"sync": { | ||
"time": { | ||
"field": "order_date", | ||
"delay": "60s" | ||
} | ||
} | ||
} | ||
-------------------------------------------------- | ||
// CONSOLE | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there is another level between sync and field/delay, its "sync" -> "time" -> "field"/"delay" (see your example below)
sync defines continuous mode, time defines that the sync method is using a timestamp field in the data. In future we will have other ways to sync source and dest, e.g. for non timeseries data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I've drafted a description of that time property.