IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
SQL Translate API
editSQL Translate API
editThis functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
The SQL Translate API accepts SQL in a JSON document and translates it into native Elasticsearch queries. For example:
POST /_xpack/sql/translate { "query": "SELECT * FROM library ORDER BY page_count DESC", "fetch_size": 10 }
Which returns:
{ "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" } } ] }
Which is the request that SQL will run to provide the results. In this case, SQL will use the scroll API. If the result contained an aggregation then SQL would use the normal search API.
The request body accepts all of the fields that
the SQL REST API accepts except cursor
.