You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Zhihua Deng (Jira)" <ji...@apache.org> on 2026/01/23 07:00:00 UTC

[jira] [Updated] (HIVE-29203) get_aggr_stats_for doesn't aggregate stats when direct sql batch retrieve is enabled

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

Zhihua Deng updated HIVE-29203:
-------------------------------
    Description: 
In case of metastore.direct.sql.batch.size > 0, and number of partition names or columns in get_aggr_stats_for is bigger than the metastore.direct.sql.batch.size, then the
AggrStats from the call get_aggr_stats_for might have un-merged stats for the same column, so the aggregated stats is not correct, which can make CBO generate an outdated execution plan.

  was:
In case of metastore.direct.sql.batch.size > 0, and number of partition names or columns in get_aggr_stats_for is bigger than the metastore.direct.sql.batch.size, then the
AggrStats from the call get_aggr_stats_for might have un-merged stats for the same column, so the aggregated stats is not correct, which may make CBO generate an outdated execution plan.


> get_aggr_stats_for doesn't aggregate stats when direct sql batch retrieve is enabled
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-29203
>                 URL: https://issues.apache.org/jira/browse/HIVE-29203
>             Project: Hive
>          Issue Type: Bug
>          Components: Standalone Metastore
>    Affects Versions: 4.2.0
>            Reporter: Zhihua Deng
>            Assignee: Ramit Gupta
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.3.0
>
>
> In case of metastore.direct.sql.batch.size > 0, and number of partition names or columns in get_aggr_stats_for is bigger than the metastore.direct.sql.batch.size, then the
> AggrStats from the call get_aggr_stats_for might have un-merged stats for the same column, so the aggregated stats is not correct, which can make CBO generate an outdated execution plan.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)