[
https://issues.apache.org/jira/browse/HIVE-5189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076520#comment-14076520
]
Sergey Shelukhin commented on HIVE-5189:
----------------------------------------
Note: issue may also help with some direct SQL issues where underlying RDBMS
may fail on a very large IN (...) query.
> make batching in partition retrieval in metastore applicable to more methods
> ----------------------------------------------------------------------------
>
> Key: HIVE-5189
> URL: https://issues.apache.org/jira/browse/HIVE-5189
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Reporter: Sergey Shelukhin
>
> As indicated in HIVE-5158, Metastore can OOM if retrieving a large number of
> partitions. For client-side partition filtering, the client applies batching
> (that would avoid that) by sending parts of the filtered name list in
> separate request according to configuration.
> The batching is not used on filter pushdown path, and when retrieving all
> partitions (e.g. when the pruner expression is not useful in non-strict
> mode). HIVE-4914 and pushdown improvements will make this problem somewhat
> worse by allowing more requests to go to the server.
> There needs to be some batching scheme (ideally, a somewhat generic one) that
> would be applicable to all these paths.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
