You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Vikram Ahuja (Jira)" <ji...@apache.org> on 2024/01/30 06:11:00 UTC

[jira] [Resolved] (HIVE-28002) Make hive.metastore.batch.retrieve.max property to be read from hiveconf when it is requested from HS2

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

Vikram Ahuja resolved HIVE-28002.
---------------------------------
    Fix Version/s: 4.0.0-beta-1
       Resolution: Not A Problem

> Make hive.metastore.batch.retrieve.max property to be read from hiveconf when it is requested from HS2
> ------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-28002
>                 URL: https://issues.apache.org/jira/browse/HIVE-28002
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0-beta-1
>            Reporter: Vikram Ahuja
>            Assignee: Vikram Ahuja
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 4.0.0-beta-1
>
>
> The property hive.metastore.batch.retrieve.max is used by both the client(Hs2) and the HMS when fetching objects(tables/partitions) in batches. This property is present in both hiveConf as well as metastoreConf. For some use cases in the client(Hs2), this value is referred from the metastoreConf. To change these use cases to HiveConf.java to have a set demarkation between HS2 and HMS use cases.



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