You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Shlok Srivastava (Jira)" <ji...@apache.org> on 2019/10/25 10:09:00 UTC

[jira] [Commented] (CALCITE-3437) Elasticsearch Match query is not supported

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

Shlok Srivastava commented on CALCITE-3437:
-------------------------------------------

We were facing the same issue. I have raised a PR for the issue with the above mentioned approach- For SqlStdOperatorTable.CONTAINS, calcite should build _match_ query.

> Elasticsearch Match query is not supported
> ------------------------------------------
>
>                 Key: CALCITE-3437
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3437
>             Project: Calcite
>          Issue Type: Improvement
>          Components: elasticsearch-adapter
>            Reporter: Shikha Somani
>            Priority: Major
>              Labels: QueryBuilder, calcite, elasticsearch, match, pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, Calcite only builds "term" queries for text fields on elasticsearch. It doesn't support [Match|[https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-match-query.html]] queries due to which _full-text_ or _contains_ search is not allowed.
> Expected query:
> {code:java}
> {
>   "query": {
>     "constant_score": {
>       "filter": {
>         "match": {
>           "name": "Customer Name"
>         }
>       }
>     }
>   }
> }
> {code}
>  
> Expected behavior:
> For SqlStdOperatorTable.CONTAINS, calcite should build _match_ query.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)