[
https://issues.apache.org/jira/browse/CALCITE-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16733228#comment-16733228
]
Michael Mior commented on CALCITE-2760:
---------------------------------------
[~asereda] Thanks for taking this one on :) I'm somewhat confused by the
changes you made though. It looks like the ElasticsearchSort will still be
created when a mapping does not exist. I would expect this to return incorrect
results when the query is executed since this sort will actually do nothing. In
this case, I would have thought the rule would need to be modified so this sort
would not be created (and other rules would create an EnumerableSort instead).
> 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)
