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

Posted to issues@impala.apache.org by "Vuk Ercegovac (JIRA)" <ji...@apache.org> on 2017/09/06 16:44:00 UTC

[jira] [Resolved] (IMPALA-1641) Changing the location of a cached table/partition should issue corresponding HDFS un/caching directives.

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

Vuk Ercegovac resolved IMPALA-1641.
-----------------------------------
    Resolution: Resolved

Always uncaching the source location and caching the target location could lead to surprises, so we're keeping the current behavior for now.

> Changing the location of a cached table/partition should issue corresponding HDFS un/caching directives.
> --------------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-1641
>                 URL: https://issues.apache.org/jira/browse/IMPALA-1641
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Catalog
>    Affects Versions: Impala 2.1
>            Reporter: Alexander Behm
>            Assignee: Vuk Ercegovac
>            Priority: Minor
>              Labels: newbie
>
> When executing an ALTER TABLE ... SET LOCATION statement, we currently do not account for possible caching directives on the table/partition. When modifying the location we must also make corresponding changes to the HDFS caching directives (if present).
> The relevant code is in CatalogOpExecutor.java alterTableSetLocation()



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)