Limitations

    You can only apply aggregation to fields. Aggregations cannot accept an expression as a parameter. For example, is not supported.

    Subquery in the FROM clause in this format: SELECT outer FROM (SELECT inner) is supported only when the query is merged into one query. For example, the following query is supported:

    The join query does not support aggregations on the joined result. For example, e.g. SELECT depo.name, avg(empo.age) FROM empo JOIN depo WHERE empo.id == depo.id GROUP BY depo.name is not supported.

    The pagination query enables you to get back paginated responses.

    The response in JDBC format with cursor id.

    The query with aggregation and join does not support pagination for now.

    • The select literal expression without FROM clause is not supported. For example, SELECT 1 is not supported.
    • The WHERE clause does not support expressions. For example, SELECT FlightNum FROM opensearch_dashboards_sample_data_flights where (AvgTicketPrice + 100) <= 1000 is not supported.

    Such queries are successfully executed by the engine unless they have V1-specific functions. You will likely never meet these limitations.

    V2 engine limitations

    • The is supported by the V1 engine only. For support of cursor/pagination in the V2 engine, track GitHub issue #656.
    • The V2 engine does not track query execution time, so slow queries are not reported.
    • The V2 query engine not only runs queries in the OpenSearch engine but also supports post-processing for complicated queries. Accordingly, the explain output is no longer pure OpenSearch domain-specific language (DSL) but also includes query plan information from the V2 query engine.
    • The V2 engine does not support and WILDCARD_QUERY functions.