[
https://issues.apache.org/jira/browse/IMPALA-4364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17163993#comment-17163993
]
Peter Ebert commented on IMPALA-4364:
-------------------------------------
One possible solution would be to add an optional location keyword to the end
of the refresh command:
refresh table_name location
Then normal refreshes wouldn't have the extra overhead of checking every path,
but if needed it could be applied.
> REFRESH does not pick up ALTER TABLE...PARTITION...SET LOCATION changes
> -----------------------------------------------------------------------
>
> Key: IMPALA-4364
> URL: https://issues.apache.org/jira/browse/IMPALA-4364
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.6.0
> Reporter: Jacob Evan Beard
> Priority: Major
> Labels: usability
>
> AFAIK the REFRESH command should pick up all changes to a table made by ALTER
> TABLE from outside of Impala (e.g. Spark SQL), however REFRESH does not pick
> up changes from ALTER TABLE...PARTITION...SET LOCATION, which seems to
> require an INVALIDATE METADATA instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
