[jira] [Commented] (HIVE-17627) Use druid scan query instead of the select query.

["Ashutosh Chauhan (JIRA)" <ji...@apache.org>]

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

Ashutosh Chauhan commented on HIVE-17627:
-----------------------------------------

[~bslim] You were reviewing this. Is this ready for commit or does this need more work?

> Use druid scan query instead of the select query.
> -------------------------------------------------
>
>                 Key: HIVE-17627
>                 URL: https://issues.apache.org/jira/browse/HIVE-17627
>             Project: Hive
>          Issue Type: Bug
>          Components: Druid integration
>            Reporter: slim bouguerra
>            Assignee: Nishant Bangarwa
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17627.1.patch, HIVE-17627.2.patch, HIVE-17627.patch
>
>
> 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.
> It will cause memory pressure if too many rows required by select query.
> Scan query doesn't have this issue.
> Scan query can 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
(v7.6.3#76005)