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: docs/overlays/elasticsearch-serverless-openapi-overlays.yaml
+31-31Lines changed: 31 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -64,34 +64,34 @@ actions:
64
64
* No manual migrations: Data, indices, and resources are migrated transparently without user intervention.
65
65
* New features available everywhere: Compatible additions like new APIs and parameters work across all supported versions.
66
66
* Predictable upgrade timeline: API versions are supported for at least 18 months after newer versions are introduced.
67
-
68
-
## API version format
69
-
70
-
API versions use ISO8601 date format: `YYYY-MM-DD`(for example, `2023-10-31`).
71
-
72
-
## Supported versions
73
-
74
-
Elasticsearch Serverless currently supports the following API versions:
75
-
76
-
* `2023-10-31`
77
-
78
-
Future breaking changes will introduce new date-based versions.
79
-
Support policies for existing versions will be announced when new versions are released.
80
-
81
-
## How to specify API versions
82
-
83
-
Clients specify API versions using the `Elastic-Api-Version` HTTP header:
84
-
85
-
```
86
-
GET /_search HTTP/1.1
87
-
Elastic-Api-Version: 2023-10-31
88
-
```
89
-
90
-
### Server responses
91
-
92
-
The server's response depends on whether the client provides a version header:
93
-
94
-
* When a client sends the `Elastic-Api-Version` header, the server processes the request using the specified API version or returns HTTP 400 if the version is unsupported or malformed.
95
-
* When no version header is provided, the server defaults to the latest supported API version.
96
-
97
-
The server always includes the Elastic-Api-Version header in successful responses to indicate which version was used.
67
+
68
+
## API version format
69
+
70
+
API versions use ISO8601 date format: `YYYY-MM-DD` (for example, `2023-10-31`).
71
+
72
+
## Supported versions
73
+
74
+
Elasticsearch Serverless currently supports the following API versions:
75
+
76
+
* `2023-10-31`
77
+
78
+
Future breaking changes will introduce new date-based versions.
79
+
Support policies for existing versions will be announced when new versions are released.
80
+
81
+
## How to specify API versions
82
+
83
+
Clients specify API versions using the `Elastic-Api-Version` HTTP header:
84
+
85
+
```
86
+
GET /_search HTTP/1.1
87
+
Elastic-Api-Version: 2023-10-31
88
+
```
89
+
90
+
### Server responses
91
+
92
+
The server's response depends on whether the client provides a version header:
93
+
94
+
* When a client sends the `Elastic-Api-Version` header, the server processes the request using the specified API version or returns HTTP 400 if the version is unsupported or malformed.
95
+
* When no version header is provided, the server defaults to the latest supported API version.
96
+
97
+
The server always includes the Elastic-Api-Version header in successful responses to indicate which version was used.
0 commit comments