@@ -61,12 +61,12 @@ A {dfeed} resource has the following properties:
61
61
62
62
`delayed_data_check_config`::
63
63
(object) Specifies whether the data feed checks for missing data and
64
- and the size of the window. For example:
64
+ the size of the window. For example:
65
65
`{"enabled": true, "check_window": "1h"}` See
66
66
<<ml-datafeed-delayed-data-check-config>>.
67
67
68
68
[[ml-datafeed-chunking-config]]
69
- ==== Chunking Configuration Objects
69
+ ==== Chunking configuration objects
70
70
71
71
{dfeeds-cap} might be required to search over long time periods, for several months
72
72
or years. This search is split into time chunks in order to ensure the load
@@ -88,31 +88,33 @@ A chunking configuration object has the following properties:
88
88
For example: `3h`.
89
89
90
90
[[ml-datafeed-delayed-data-check-config]]
91
- ==== Delayed Data Check Configuration Objects
91
+ ==== Delayed data check configuration objects
92
92
93
93
The {dfeed} can optionally search over indices that have already been read in
94
- an effort to find if any data has since been added to the index. If missing data
95
- is found, it is a good indication that the `query_delay` option is set too low and
96
- the data is being indexed after the {dfeed} has passed that moment in time. See
94
+ an effort to determine whether any data has subsequently been added to the index.
95
+ If missing data is found, it is a good indication that the `query_delay` option
96
+ is set too low and the data is being indexed after the {dfeed} has passed that
97
+ moment in time. See
97
98
{stack-ov}/ml-delayed-data-detection.html[Working with delayed data].
98
99
99
- This check only runs on real-time {dfeeds}
100
+ This check runs only on real-time {dfeeds}.
100
101
101
102
The configuration object has the following properties:
102
103
103
104
`enabled`::
104
- (boolean) Should the {dfeed} periodically check for data being indexed after reading .
105
- Defaults to `true`
105
+ (boolean) Specifies whether the {dfeed} periodically checks for delayed data .
106
+ Defaults to `true`.
106
107
107
108
`check_window`::
108
- (time units) The window of time before the latest finalized bucket that should be searched
109
- for late data. Defaults to `null` which causes an appropriate `check_window` to be calculated
110
- when the real-time {dfeed} runs.
111
- The default `check_window` span calculation is the max between `2h` or `8 * bucket_span`.
109
+ (time units) The window of time that is searched for late data. This window of
110
+ time ends with the latest finalized bucket. It defaults to `null`, which
111
+ causes an appropriate `check_window` to be calculated when the real-time
112
+ {dfeed} runs. In particular, the default `check_window` span calculation is
113
+ based on the maximum of `2h` or `8 * bucket_span`.
112
114
113
115
[float]
114
116
[[ml-datafeed-counts]]
115
- ==== {dfeed-cap} Counts
117
+ ==== {dfeed-cap} counts
116
118
117
119
The get {dfeed} statistics API provides information about the operational
118
120
progress of a {dfeed}. All of these properties are informational; you cannot
0 commit comments