You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "yunfeng (Jira)" <ji...@apache.org> on 2019/10/24 07:34:00 UTC
[jira] [Updated] (CALCITE-3442) Set `stored_fields = _none`
prohibit `FetchPhase` get be involved and improve the performance for
Elasticsearch
[ https://issues.apache.org/jira/browse/CALCITE-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yunfeng updated CALCITE-3442:
-----------------------------
Summary: Set `stored_fields = _none` prohibit `FetchPhase` get be involved and improve the performance for Elasticsearch (was: Set `stored_fields = _none` prohibit `FetchPhase` get be involved and improve the Performance for Elasticsearch)
> Set `stored_fields = _none` prohibit `FetchPhase` get be involved and improve the performance for Elasticsearch
> ---------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-3442
> URL: https://issues.apache.org/jira/browse/CALCITE-3442
> Project: Calcite
> Issue Type: Improvement
> Components: elasticsearch-adapter
> Reporter: yunfeng
> Priority: Major
> Labels: performance, pull-request-available
> Fix For: next
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For elasticsearch-adapte, when ElasticsearchAggregat 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 completely
--
This message was sent by Atlassian Jira
(v8.3.4#803005)