Peng Huo

Thanks for reporting the issue. Checking now.

Hi, Have you checked the https://opendistro.github.io/for-elasticsearch-docs/docs/security/access-control/field-level-security/, the ODFE release already supported field level security.

Thanks for reporting the issue. The IN operator is not supported in our [new engine](https://github.com/opendistro-for-elasticsearch/sql/blob/develop/docs/dev/NewSQLEngine.md), at runtime, it will [fallback](https://github.com/opendistro-for-elasticsearch/sql/blob/develop/docs/dev/NewSQLEngine.md#32-fallback-mechanism) to the old engine. We will prioritize this feature in...

Could you try this? ``` SELECT dest_city_name AS dc FROM all_flights WHERE dest_city_name IS NOT NULL ``` dc is output symbol, only symbol defined in all_flights visible to SQL engine...

similar issue in opendistrocommunity. https://discuss.opendistrocommunity.dev/t/sql-plugin-date-filter-causes-error/4883

Hi FreCap, Thanks for reporting this breaking issue. In the new engine released on 1.13, we don't support type auto casting. The reason it works in old engine are 1....

[size:3 is the default setting](https://www.elastic.co/guide/en/elasticsearch/reference/6.8/search-request-inner-hits.html) of inner_hits builder. https://github.com/opendistro-for-elasticsearch/sql/blob/develop/legacy/src/main/java/com/amazon/opendistroforelasticsearch/sql/legacy/rewriter/nestedfield/NestedFieldProjection.java#L143

REST "opendistro.sql.engine.nested.limit": 100 with default = 10 more make sense to me.

Could we refactor source/search command to let user provide promql directly? for example, ``` source=promql(http_requests_total{job="apiserver", handler="/api/comments"}) ``` The benefit is user could still use the familiar promql. It is easy...

Try to reproduce the issue in Dev Tools. SQL engine throw exception when reading data from OpenSearch, it found a field body.gender missing type information. Here is a workaround. *...