hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-19423) REPL LOAD creates staging directory in source dump directory instead of table data location
Date Wed, 24 Jun 2020 00:28:01 GMT

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

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

                Author: ASF GitHub Bot
            Created on: 24/Jun/20 00:27
            Start Date: 24/Jun/20 00:27
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] closed pull request #340:
URL: https://github.com/apache/hive/pull/340


   


----------------------------------------------------------------
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.

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


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

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

> REPL LOAD creates staging directory in source dump directory instead of table data location
> -------------------------------------------------------------------------------------------
>
>                 Key: HIVE-19423
>                 URL: https://issues.apache.org/jira/browse/HIVE-19423
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive, HiveServer2, repl
>            Reporter: mahesh kumar behera
>            Assignee: mahesh kumar behera
>            Priority: Major
>              Labels: Hive, Repl, pull-request-available
>             Fix For: 3.0.0, 3.1.0
>
>         Attachments: HIVE-19423.01.patch, HIVE-19423.02.patch
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> REPL LOAD creates staging directory in source dump directory instead of table data location.
In case of replication from on-perm to cloud it can create problem. 



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

Mime
View raw message