[jira] [Commented] (CALCITE-2760) Elasticsearch adapter can't sort on umapped fields

["Andrei Sereda (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16732166#comment-16732166 ] 

Andrei Sereda commented on CALCITE-2760:
----------------------------------------

[~michaelmior] this should be fixed after CALCITE-2755
We're now keeping mapping between expression and item call. For more context see [thread on dev list|https://lists.apache.org/thread.html/91ac1a5215e22afa9abee924426e05cfbcf257aae6858741308ed7b8@%3Cdev.calcite.apache.org%3E]

> Elasticsearch adapter can't sort on umapped fields
> --------------------------------------------------
>
>                 Key: CALCITE-2760
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2760
>             Project: Calcite
>          Issue Type: Bug
>          Components: elasticsearch-adapter
>    Affects Versions: 1.17.0
>            Reporter: Michael Mior
>            Assignee: Julian Hyde
>            Priority: Major
>
> When trying to sort on unmapped fields, the adapter throws an exception. It seems like {{ElasticsearchSortRule}} should check if the field is mapped before it is applied so the sort can be performed by Calcite if Elasticsearch can't do it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)