root
/
elasticsearch
mirror of https://github.com/elastic/elasticsearch.git
1
0
Fork 0
Code Issues Actions 1 Packages Projects Releases Wiki Activity
elasticsearch/docs/reference/esql/source-commands/show.asciidoc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

36 lines
694 B
Plaintext
Raw Normal View History

Restructure ES|QL docs (#100806) * Break out 'Limitations' into separate page * Add REST API docs * Restructure commands, functions, and operators refs * Add placeholder for getting started guide * Group 'Syntax', 'Metafields', and 'MV fields' under 'Language' * Add placeholder for Kibana page * Add link from landing page * Apply uniform formatting to ACOS, CASE, and DATE_PARSE function refs * Reword default LIMIT * Add support for COUNT(*) * Move 'Commands' and 'Functions and operators' to individual pages --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2023-10-17 23:36:14 +08:00
[discrete]
Docs: move source commands into a file per command (ESQL-1191) I think it's a bit easier to deal with the files this way. They also make a page per command so it lines up with the files which is nice. Also I moved some of the examples into the docs. They were mostly there already, but I linked them. --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
2023-05-30 19:58:33 +08:00
[[esql-show]]
[DOCS] Uniform formatting for ES|QL commands (#101728) * Source commands * Missing word * Processing commands * Apply suggestions from code review Co-authored-by: Alexander Spies <alexander.spies@elastic.co> * Review feedback * Add sort detail for mv * More review feedback --------- Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
2023-11-06 15:42:13 +08:00
=== `SHOW`
Docs: move source commands into a file per command (ESQL-1191) I think it's a bit easier to deal with the files this way. They also make a page per command so it lines up with the files which is nice. Also I moved some of the examples into the docs. They were mostly there already, but I linked them. --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
2023-05-30 19:58:33 +08:00
[DOCS] Uniform formatting for ES|QL commands (#101728) * Source commands * Missing word * Processing commands * Apply suggestions from code review Co-authored-by: Alexander Spies <alexander.spies@elastic.co> * Review feedback * Add sort detail for mv * More review feedback --------- Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
2023-11-06 15:42:13 +08:00
**Syntax**
[source,esql]
----
SHOW item
----
*Parameters*
`item`::
ESQL: Mark a few features as experimental (#105263) Mark the following features as experimental in the docs: * `AUTO_BUCKET()` * `SHOW FUNCTIONS` * unsigned_long type
2024-02-08 09:28:13 +08:00
Can be `INFO` or experimental:[] `FUNCTIONS`.
[DOCS] Uniform formatting for ES|QL commands (#101728) * Source commands * Missing word * Processing commands * Apply suggestions from code review Co-authored-by: Alexander Spies <alexander.spies@elastic.co> * Review feedback * Add sort detail for mv * More review feedback --------- Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
2023-11-06 15:42:13 +08:00
*Description*
The `SHOW` source command returns information about the deployment and
Docs: move source commands into a file per command (ESQL-1191) I think it's a bit easier to deal with the files this way. They also make a page per command so it lines up with the files which is nice. Also I moved some of the examples into the docs. They were mostly there already, but I linked them. --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
2023-05-30 19:58:33 +08:00
its capabilities:
* Use `SHOW INFO` to return the deployment's version, build date and hash.
ESQL: Mark a few features as experimental (#105263) Mark the following features as experimental in the docs: * `AUTO_BUCKET()` * `SHOW FUNCTIONS` * unsigned_long type
2024-02-08 09:28:13 +08:00
* Use experimental:[] `SHOW FUNCTIONS` to return a list of all supported functions and a
Docs: move source commands into a file per command (ESQL-1191) I think it's a bit easier to deal with the files this way. They also make a page per command so it lines up with the files which is nice. Also I moved some of the examples into the docs. They were mostly there already, but I linked them. --------- Co-authored-by: Abdon Pijpelink <abdon.pijpelink@elastic.co>
2023-05-30 19:58:33 +08:00
synopsis of each function.
[DOCS] Uniform formatting for ES|QL commands (#101728) * Source commands * Missing word * Processing commands * Apply suggestions from code review Co-authored-by: Alexander Spies <alexander.spies@elastic.co> * Review feedback * Add sort detail for mv * More review feedback --------- Co-authored-by: Alexander Spies <alexander.spies@elastic.co>
2023-11-06 15:42:13 +08:00
*Examples*
[source.merge.styled,esql]
----
include::{esql-specs}/show.csv-spec[tag=showFunctionsFiltered]
----
[%header.monospaced.styled,format=dsv,separator=|]
|===
include::{esql-specs}/show.csv-spec[tag=showFunctionsFiltered-result]
|===