mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-08 05:58:44 +00:00
52104aac27
Make SQL aware of missing and/or unmapped fields treating them as NULL Make _all_ functions and operators null-safe aware, including when used in filtering or sorting contexts Add missing and null-safe doc value extractor Modify dataset to have null fields spread around (in groups of 10) Enforce missing last and unmapped_type inside sorting Consolidate Predicate templating and declaration Add support for Like/RLike in scripting Generalize NULLS LAST/FIRST Introduce early schema declaration for CSV spec tests: to keep the doc snippets in place (introduce schema:: prefix for declaration) upfront. Fix #32079
63 lines
1.5 KiB
Plaintext
63 lines
1.5 KiB
Plaintext
[role="xpack"]
|
|
[testenv="basic"]
|
|
[[sql-translate]]
|
|
== SQL Translate API
|
|
|
|
The SQL Translate API accepts SQL in a JSON document and translates it
|
|
into native Elasticsearch queries. For example:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
POST /_xpack/sql/translate
|
|
{
|
|
"query": "SELECT * FROM library ORDER BY page_count DESC",
|
|
"fetch_size": 10
|
|
}
|
|
--------------------------------------------------
|
|
// CONSOLE
|
|
// TEST[setup:library]
|
|
|
|
Which returns:
|
|
|
|
[source,js]
|
|
--------------------------------------------------
|
|
{
|
|
"size" : 10,
|
|
"docvalue_fields" : [
|
|
{
|
|
"field": "page_count",
|
|
"format": "use_field_mapping"
|
|
},
|
|
{
|
|
"field": "release_date",
|
|
"format": "epoch_millis"
|
|
}
|
|
],
|
|
"_source": {
|
|
"includes": [
|
|
"author",
|
|
"name"
|
|
],
|
|
"excludes": []
|
|
},
|
|
"sort" : [
|
|
{
|
|
"page_count" : {
|
|
"order" : "desc",
|
|
"missing" : "_first",
|
|
"unmapped_type" : "short"
|
|
}
|
|
}
|
|
]
|
|
}
|
|
--------------------------------------------------
|
|
// TESTRESPONSE
|
|
|
|
Which is the request that SQL will run to provide the results.
|
|
In this case, SQL will use the <<search-request-scroll,scroll>>
|
|
API. If the result contained an aggregation then SQL would use
|
|
the normal <<search-request-body,search>> API.
|
|
|
|
The request body accepts all of the <<sql-rest-fields,fields>> that
|
|
the <<sql-rest,SQL REST API>> accepts except `cursor`.
|