hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-20152) reset db state, when repl dump fails, so rename table can be done
Date Tue, 17 Jul 2018 11:10:00 GMT


Hive QA commented on HIVE-20152:

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14662 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12931897 - PreCommit-HIVE-Build

> reset db state, when repl dump fails, so rename table can be done
> -----------------------------------------------------------------
>                 Key: HIVE-20152
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: HiveServer2
>    Affects Versions: 3.0.0
>            Reporter: anishek
>            Assignee: anishek
>            Priority: Critical
>              Labels: pull-request-available
>         Attachments: HIVE-20152.1.patch, HIVE-20152.2.patch, HIVE-20152.3.patch, HIVE-20152.4.patch
> If a repl dump command is run and it fails for some reason while doing table level dumps,
the state set on the db parameters is not reset and hence no table / partition renames can
be done. 
> the property to be reset is prefixed with key {code}bootstrap.dump.state {code}
> and it should be unset. meanwhile the workaround is 
> {code}
> describe database extended [db_name]; 
> {code}
> assuming property is 'bootstrap.dump.state.something'
> {code}
> alter  database [db_name] set dbproperties ('bootstrap.dump.state.something'='idle');"
> {code}

This message was sent by Atlassian JIRA

View raw message