[ 
https://issues.apache.org/jira/browse/IMPALA-3796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17254334#comment-17254334
 ] 

Vihang Karajgaonkar commented on IMPALA-3796:
---------------------------------------------

Recover partitions is probably not the right usage here since it is used to 
discover new partitions. A refresh table command is more appropriate. We 
introduced a query option recently {{REFRESH_UPDATED_HMS_PARTITIONS}} which 
will refresh such partitions when locations are changed. I am resolving this as 
duplicate of IMPALA-4364

> Alter table recover partitions fails to detect changes in parent path
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-3796
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3796
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: Impala 2.3.0
>            Reporter: Peter Ebert
>            Priority: Minor
>              Labels: ramp-up, usability
>
> If you have a table located at /db/table
> with partitions /db/table/partition=1
> and then move the table location to /db2/table/ along with the partitions and 
> their data
> the location of the partitions will be incorrect when you list them, still 
> pointing to /db/table/partition=1
> running a "Alter table recover partitions" seems to check only for the 
> existence of partition=1 in the +current+ table location, and ignores that 
> the prior path has changed. So when you run a query it will not find those 
> partitions and report 0 rows.
> it should be noted that hive has the same behavior.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to