You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2017/12/21 20:28:00 UTC
[jira] [Resolved] (CALCITE-2077) Druid adapter: Use "scan" query
rather than "select" query
[ https://issues.apache.org/jira/browse/CALCITE-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesus Camacho Rodriguez resolved CALCITE-2077.
----------------------------------------------
Resolution: Fixed
Fix Version/s: 1.16.0
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/159bcab . Thanks [~nishantbangarwa]
> Druid adapter: Use "scan" query rather than "select" query
> ----------------------------------------------------------
>
> Key: CALCITE-2077
> URL: https://issues.apache.org/jira/browse/CALCITE-2077
> Project: Calcite
> Issue Type: Improvement
> Components: druid
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Fix For: 1.16.0
>
>
> The biggest difference between select query and scan query is that, scan query doesn't retain all rows in memory before rows can be returned to client.
> Select query on very large segments will cause memory pressure on druid historicals if too many rows required by select query whereas Scan query doesn't have this issue.
> Scan query can also return all rows without issuing another pagination query, which is extremely useful when query against historical or realtime node directly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)