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/reference/query-languages/esql/_snippets/commands/layout/completion.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ COMPLETION [column =] prompt WITH inference_id
28
28
: The ID of the [inference endpoint](docs-content://explore-analyze/elastic-inference/inference-api.md) to use for the task.
29
29
The inference endpoint must be configured with the `completion` task type.
30
30
31
-
## Description
31
+
### Description
32
32
33
33
The `COMPLETION` command provides a general-purpose interface for
34
34
text generation tasks using a Large Language Model (LLM) in ES|QL.
@@ -43,13 +43,13 @@ including:
43
43
- Content rewriting
44
44
- Creative generation
45
45
46
-
## Requirements
46
+
### Requirements
47
47
48
48
To use this command, you must deploy your LLM model in Elasticsearch as
49
49
an [inference endpoint](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-inference-put) with the
50
50
task type `completion`.
51
51
52
-
### Handling timeouts
52
+
#### Handling timeouts
53
53
54
54
`COMPLETION` commands may time out when processing large datasets or complex prompts. To increase timeout limits for these operations, the configuration methods vary by deployment type:
0 commit comments