[ 
https://issues.apache.org/jira/browse/CALCITE-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Danny Chen resolved CALCITE-3442.
---------------------------------
    Fix Version/s:     (was: next)
                   1.22.0
         Assignee: Danny Chen
       Resolution: Fixed

Fixed in 
[1ef2821|https://github.com/apache/calcite/commit/1ef2821695ca6e10fbad7b8efe7246c4a20143af],
 thanks for your PR, [~yunfeng,wu] !

> In ElasticSearch adapter, set `stored_fields = _none_` to prohibit FetchPhase 
> get involved
> ------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-3442
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3442
>             Project: Calcite
>          Issue Type: Improvement
>          Components: elasticsearch-adapter
>            Reporter: yunfeng
>            Assignee: Danny Chen
>            Priority: Major
>              Labels: performance, pull-request-available
>             Fix For: 1.22.0
>
>         Attachments: elasticsearch-adapter.diff
>
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
>  For elasticsearch-adapter,   when  ElasticsearchAggregate  involved , set 
> _source = false and size = 0 , Elasticsearch `FetchPhase` would still be 
> executed against the current  search process and visit the Lucene 
> stored_fields, which would lead to performance declined dramatically.  
> We can set `stored_fields = _none` prohibit this such behavior entirely, and 
> skip the Elasticsearch's `fetch phase` which would bring time-consuming  
> `fetch phase` for  metadata fields such as '_id' etc. 



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

Reply via email to