[ 
https://issues.apache.org/jira/browse/HIVE-25324?focusedWorklogId=622058&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-622058
 ]

ASF GitHub Bot logged work on HIVE-25324:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 13/Jul/21 15:34
            Start Date: 13/Jul/21 15:34
    Worklog Time Spent: 10m 
      Work Description: prasanthj commented on pull request #2470:
URL: https://github.com/apache/hive/pull/2470#issuecomment-879191568


   Removing PartitionManagementTask class from metastore.task.threads.remote 
config provides the same effect (disabling)? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: gitbox-unsubscr...@hive.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 622058)
    Time Spent: 20m  (was: 10m)

> Add option to disable PartitionManagementTask
> ---------------------------------------------
>
>                 Key: HIVE-25324
>                 URL: https://issues.apache.org/jira/browse/HIVE-25324
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>            Reporter: Rajesh Balamohan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When large number of tables (e.g 2000) and databases are present, 
> PartitionManagementTask scans all tables and partitions causing pressure on 
> HMS.
> Currently there is no way to disable PartitionManagementTask as well. Round 
> about option is to provide pattern via 
> "metastore.partition.management.database.pattern / 
> metastore.partition.management.table.pattern".
> It will be good to provide an option to disable it completely.{color:#807d6e}
> {color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to