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
Copy file name to clipboardExpand all lines: serverless/pages/developer-tools-troubleshooting.mdx
+11-18Lines changed: 11 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,21 +16,14 @@ Elasticsearch returns an `index_not_found_exception` when the data stream, index
16
16
or alias you try to query does not exist. This can happen when you misspell the
17
17
name or when the data has been indexed to a different data stream or index.
18
18
19
-
Use the [**Exists API**](/api-reference/search/indices-exists) to check whether
19
+
Use the [**Exists API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-exists-index-template) to check whether
20
20
a data stream, index, or alias exists:
21
21
22
22
```js
23
-
HEAD my-data-stream
23
+
HEAD my-index
24
24
```
25
25
26
-
Use the [**Data stream stats API**](/api-reference/search/indices-data-streams-stats)
27
-
to list all data streams:
28
-
29
-
```js
30
-
GET/_data_stream/_stats
31
-
```
32
-
33
-
Use the [**Get index API**](/api-reference/search/indices-get)
26
+
Use the [**Get index API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-get)
34
27
to list all indices and their aliases:
35
28
36
29
```js
@@ -53,7 +46,7 @@ This can happen when there is a data ingestion issue.
53
46
For example, the data may have been indexed to a data stream or index with
54
47
another name.
55
48
56
-
Use the [**Count API**](/api-reference/search/count-3)
49
+
Use the [**Count API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-count-1)
57
50
to retrieve the number of documents in a data
58
51
stream or index.
59
52
Check that `count` in the response is not 0.
@@ -73,7 +66,7 @@ configured with the correct time field.
73
66
## Check that the field exists and its capabilities
74
67
75
68
Querying a field that does not exist will not return any results.
76
-
Use the [**Field capabilities API**](/api-reference/search/field-caps)
69
+
Use the [**Field capabilities API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-field-caps)
77
70
to check whether a field exists:
78
71
79
72
```js
@@ -110,15 +103,15 @@ searchable and aggregatable.
110
103
## Check the field's mappings
111
104
112
105
A field's capabilities are determined by its [mapping](((ref))/mapping.html).
113
-
To retrieve the mapping, use the [**Get mapping API**](/api-reference/search/indices-get-mapping-1):
106
+
To retrieve the mapping, use the [**Get mapping API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-get-mapping):
114
107
115
108
```js
116
109
GET/my-index-000001/_mappings
117
110
```
118
111
119
112
If you query a `text` field, pay attention to the analyzer that may have been
120
113
configured.
121
-
You can use the [**Analyze API**](/api-reference/search/indices-analyze)
114
+
You can use the [**Analyze API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-analyze)
122
115
to check how a field's analyzer processes values and query terms:
123
116
124
117
```js
@@ -129,7 +122,7 @@ GET /my-index-000001/_analyze
129
122
}
130
123
```
131
124
132
-
To change the mapping of an existing field use the [**Update mapping API**](/api-reference/search/indices-put-mapping).
125
+
To change the mapping of an existing field use the [**Update mapping API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-put-mapping-1).
133
126
134
127
## Check the field's values
135
128
@@ -203,7 +196,7 @@ GET /my-index-000001/_search?sort=@timestamp:desc&size=1
203
196
When a query returns unexpected results, Elasticsearch offers several tools to
204
197
investigate why.
205
198
206
-
The [**Validate API**](/api-reference/search/indices-validate-query-2)
199
+
The [**Validate API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-validate-query)
207
200
enables you to validate a query.
208
201
Use the `rewrite` parameter to return the Lucene query an Elasticsearch query is
209
202
rewritten into:
@@ -251,15 +244,15 @@ Index settings {/* <DocLink id="enElasticsearchReferenceIndexModules" section="i
251
244
can influence search results.
252
245
For example, the `index.query.default_field` setting, which determines the field
253
246
that is queried when a query specifies no explicit field.
254
-
Use the [**Get index settings API**](/api-reference/search/indices-get-settings-1)
247
+
Use the [**Get index settings API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-get-settings)
255
248
to retrieve the settings for an index:
256
249
257
250
```bash
258
251
GET/my-index-000001/_settings
259
252
```
260
253
261
254
You can update dynamic index settings with the
262
-
[**Update index settings API**](/api-reference/search/indices-put-settings-1).
255
+
[**Update index settings API**](https://www.elastic.co/docs/api/doc/elasticsearch-serverless/operation/operation-indices-put-settings).
263
256
Changing dynamic index settings for a data stream
264
257
{/* <DocLink id="enElasticsearchReferenceModifyDataStreams" section="change-a-dynamic-index-setting-for-a-data-stream">Changing dynamic index settings for a data stream</DocLink> */} requires changing the index template used by the data stream.
0 commit comments