You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// This should have been written with capital letters, it's a known typo and should not be corrected.
36
-
datastream="Data stream lifecycle",
37
-
unmanaged="Unmanaged",
36
+
datastream='Data stream lifecycle',
37
+
unmanaged='Unmanaged'
38
38
}
39
39
40
40
// Available index modes (for the `index.mode` setting) See the `IndexMode` class in Elasticsearch for the options.
41
41
exportenumIndexMode{
42
42
standard,
43
43
time_series,
44
44
logsdb,
45
-
lookup,
45
+
lookup
46
46
}
47
47
48
48
exportclassFailureStore{
49
-
enabled: boolean;
50
-
indices: DataStreamIndex[];
51
-
rollover_on_write: boolean;
49
+
enabled: boolean
50
+
indices: DataStreamIndex[]
51
+
rollover_on_write: boolean
52
52
}
53
53
54
54
exportclassDataStream{
@@ -57,128 +57,128 @@ export class DataStream {
57
57
* If empty, the response omits this property.
58
58
* @doc_id mapping-meta-field
59
59
*/
60
-
_meta?: Metadata;
60
+
_meta?: Metadata
61
61
/**
62
62
* If `true`, the data stream allows custom routing on write request.
63
63
*/
64
-
allow_custom_routing?: boolean;
64
+
allow_custom_routing?: boolean
65
65
/**
66
66
* Information about failure store backing indices
67
67
*
68
68
*/
69
-
failure_store?: FailureStore;
69
+
failure_store?: FailureStore
70
70
/**
71
71
* Current generation for the data stream. This number acts as a cumulative count of the stream’s rollovers, starting at 1.
72
72
*/
73
-
generation: integer;
73
+
generation: integer
74
74
/**
75
75
* If `true`, the data stream is hidden.
76
76
*/
77
-
hidden: boolean;
77
+
hidden: boolean
78
78
/**
79
79
* Name of the current ILM lifecycle policy in the stream’s matching index template.
80
80
* This lifecycle policy is set in the `index.lifecycle.name` setting.
81
81
* If the template does not include a lifecycle policy, this property is not included in the response.
82
82
* NOTE: A data stream’s backing indices may be assigned different lifecycle policies. To retrieve the lifecycle policy for individual backing indices, use the get index settings API.
83
83
*/
84
-
ilm_policy?: Name;
84
+
ilm_policy?: Name
85
85
/**
86
86
* Name of the lifecycle system that'll manage the next generation of the data stream.
87
87
*/
88
-
next_generation_managed_by: ManagedBy;
88
+
next_generation_managed_by: ManagedBy
89
89
/**
90
90
* Indicates if ILM should take precedence over DSL in case both are configured to managed this data stream.
91
91
*/
92
-
prefer_ilm: boolean;
92
+
prefer_ilm: boolean
93
93
/**
94
94
* Array of objects containing information about the data stream’s backing indices.
95
95
* The last item in this array contains information about the stream’s current write index.
96
96
*/
97
-
indices: DataStreamIndex[];
97
+
indices: DataStreamIndex[]
98
98
/**
99
99
* Contains the configuration for the data stream lifecycle of this data stream.
* If `true`, the data stream is created and managed by cross-cluster replication and the local cluster can not write into this data stream or change its mappings.
110
110
*/
111
-
replicated?: boolean;
111
+
replicated?: boolean
112
112
/**
113
113
* If `true`, the next write to this data stream will trigger a rollover first and the document will be indexed in the new backing index. If the rollover fails the indexing request will fail too.
114
114
*/
115
-
rollover_on_write: boolean;
115
+
rollover_on_write: boolean
116
116
/**
117
117
* The settings specific to this data stream that will take precedence over the settings in the matching index
118
118
* template.
119
119
*/
120
-
settings: IndexSettings;
120
+
settings: IndexSettings
121
121
/**
122
122
* Health status of the data stream.
123
123
* This health status is based on the state of the primary and replica shards of the stream’s backing indices.
124
124
*/
125
-
status: HealthStatus;
125
+
status: HealthStatus
126
126
/**
127
127
* If `true`, the data stream is created and managed by an Elastic stack component and cannot be modified through normal user interaction.
128
128
* @availability stack since=7.10.0
129
129
* @availability serverless
130
130
*/
131
-
system?: boolean;
131
+
system?: boolean
132
132
/**
133
133
* Name of the index template used to create the data stream’s backing indices.
134
134
* The template’s index pattern must match the name of this data stream.
135
135
*/
136
-
template: Name;
136
+
template: Name
137
137
/**
138
138
* Information about the `@timestamp` field in the data stream.
139
139
*/
140
-
timestamp_field: DataStreamTimestampField;
140
+
timestamp_field: DataStreamTimestampField
141
141
/**
142
142
* The index mode for the data stream that will be used for newly created backing indices.
143
143
*/
144
-
index_mode?: IndexMode;
144
+
index_mode?: IndexMode
145
145
}
146
146
147
147
exportclassDataStreamTimestampField{
148
148
/**
149
149
* Name of the timestamp field for the data stream, which must be `@timestamp`. The `@timestamp` field must be included in every document indexed to the data stream.
150
150
*/
151
-
name: Field;
151
+
name: Field
152
152
}
153
153
154
154
exportclassDataStreamIndex{
155
155
/**
156
156
* Name of the backing index.
157
157
*/
158
-
index_name: IndexName;
158
+
index_name: IndexName
159
159
/**
160
160
* Universally unique identifier (UUID) for the index.
161
161
*/
162
-
index_uuid: Uuid;
162
+
index_uuid: Uuid
163
163
/**
164
164
* Name of the current ILM lifecycle policy configured for this backing index.
165
165
*/
166
-
ilm_policy?: Name;
166
+
ilm_policy?: Name
167
167
/**
168
168
* Name of the lifecycle system that's currently managing this backing index.
169
169
*/
170
-
managed_by?: ManagedBy;
170
+
managed_by?: ManagedBy
171
171
/**
172
172
* Indicates if ILM should take precedence over DSL in case both are configured to manage this index.
173
173
*/
174
-
prefer_ilm?: boolean;
174
+
prefer_ilm?: boolean
175
175
/**
176
176
* The index mode of this backing index of the data stream.
0 commit comments