mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-30 10:23:41 -04:00
777598d602
* [DOCS] Remove manual redirects * [DOCS] Removed refs to modules-discovery-hosts-providers * [DOCS] Fixed broken internal refs * Fixing bad cross links in ES book, and adding redirects.asciidoc[] back into docs/reference/index.asciidoc. * Update docs/reference/search/point-in-time-api.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/setup/restart-cluster.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/sql/endpoints/translate.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update docs/reference/snapshot-restore/restore-snapshot.asciidoc Co-authored-by: James Rodewig <james.rodewig@elastic.co> * Update repository-azure.asciidoc * Update node-tool.asciidoc * Update repository-azure.asciidoc --------- Co-authored-by: amyjtechwriter <61687663+amyjtechwriter@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Amy Jonsson <amy.jonsson@elastic.co> Co-authored-by: James Rodewig <james.rodewig@elastic.co>
59 lines
1.3 KiB
Text
59 lines
1.3 KiB
Text
[role="xpack"]
|
|
[[sql-translate]]
|
|
== SQL Translate API
|
|
|
|
The SQL Translate API accepts SQL in a JSON document and translates it
|
|
into native {es} queries. For example:
|
|
|
|
[source,console]
|
|
--------------------------------------------------
|
|
POST /_sql/translate
|
|
{
|
|
"query": "SELECT * FROM library ORDER BY page_count DESC",
|
|
"fetch_size": 10
|
|
}
|
|
--------------------------------------------------
|
|
// TEST[setup:library]
|
|
|
|
Which returns:
|
|
|
|
[source,console-result]
|
|
--------------------------------------------------
|
|
{
|
|
"size": 10,
|
|
"_source": false,
|
|
"fields": [
|
|
{
|
|
"field": "author"
|
|
},
|
|
{
|
|
"field": "name"
|
|
},
|
|
{
|
|
"field": "page_count"
|
|
},
|
|
{
|
|
"field": "release_date",
|
|
"format": "strict_date_optional_time_nanos"
|
|
}
|
|
],
|
|
"sort": [
|
|
{
|
|
"page_count": {
|
|
"order": "desc",
|
|
"missing": "_first",
|
|
"unmapped_type": "short"
|
|
}
|
|
}
|
|
],
|
|
"track_total_hits": -1
|
|
}
|
|
--------------------------------------------------
|
|
|
|
Which is the request that SQL will run to provide the results.
|
|
In this case, SQL will use the <<scroll-search-results,scroll>>
|
|
API. If the result contained an aggregation then SQL would use
|
|
the normal <<search-search,search API>>.
|
|
|
|
The request body accepts the same <<sql-search-api-request-body,parameters>> as
|
|
the <<sql-search-api,SQL search API>>, excluding `cursor`.
|