You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Ádám Szita (Jira)" <ji...@apache.org> on 2020/02/21 13:23:00 UTC

[jira] [Assigned] (HIVE-22380) HiveStrictManagedMigration - migration isn't triggered if database location is updated

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

Ádám Szita reassigned HIVE-22380:
---------------------------------

    Assignee: Ádám Szita

> HiveStrictManagedMigration - migration isn't triggered if database location is updated
> --------------------------------------------------------------------------------------
>
>                 Key: HIVE-22380
>                 URL: https://issues.apache.org/jira/browse/HIVE-22380
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Vineet Garg
>            Assignee: Ádám Szita
>            Priority: Major
>
> Migration could be triggered for single table, which updates the DB location. If user wants to trigger migration for another table in the database whole migration silently skips since DB location has already been updated.
> There should be an option to force migration to go ahead even if DB location is updated otherwise user is left no option to migrate rest of the tables.
>  
> cc [~jdere]



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