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

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

                Author: ASF GitHub Bot
            Created on: 27/Oct/22 00:26
            Start Date: 27/Oct/22 00:26
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] closed pull request #3477: 
HIVE-26012: HMS APIs to be enhanced for metadata replication
URL: https://github.com/apache/hive/pull/3477




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

    Worklog Id:     (was: 820778)
    Time Spent: 5h 40m  (was: 5.5h)

> HMS APIs to be enhanced for metadata replication
> ------------------------------------------------
>
>                 Key: HIVE-26012
>                 URL: https://issues.apache.org/jira/browse/HIVE-26012
>             Project: Hive
>          Issue Type: Improvement
>          Components: Metastore
>    Affects Versions: 3.1.0
>            Reporter: Naveen Gangam
>            Assignee: Hongdan Zhu
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HMS APIs to be enhanced for metadata replication.docx
>
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
>
> HMS currently has APIs like these that automatically create/delete the 
> directories on the associated DFS. 
> [create/drop]_database
> [create/drop]_table*
> [add/append/drop]_partition*
> This is expected and should be this way when query processors use this APIs. 
> However, when tools that replicate hive metadata use this APIs on the target 
> cluster, creating these dirs on target side which cause the replication of 
> DFS-snapshots to fail.
> So we if provide an option to bypass this creation of dirs, dfs replications 
> will be smoother. In the future we will need to restrict users that can use 
> these APIs. So we will have some sort of an authorization policy.



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

Reply via email to