hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nishant Bangarwa (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (HIVE-17627) Use druid scan query instead of the select query.
Date Sun, 03 Dec 2017 07:50:01 GMT

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

Nishant Bangarwa reassigned HIVE-17627:
---------------------------------------

    Assignee: Nishant Bangarwa

> 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
>
> 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
(v6.4.14#64029)

Mime
View raw message