You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/06/02 00:36:00 UTC

[jira] [Closed] (IMPALA-6020) REFRESH statement cannot detect HDFS block movement

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

Alex Rodoni closed IMPALA-6020.
-------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0
                   Impala 2.13.0

> REFRESH statement cannot detect HDFS block movement
> ---------------------------------------------------
>
>                 Key: IMPALA-6020
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6020
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: Impala 2.8.0, Impala 2.9.0, Impala 2.10.0
>            Reporter: Jim Apple
>            Assignee: Alex Rodoni
>            Priority: Major
>             Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> In the release notes, it says
> http://impala.apache.org/docs/build/html/topics/impala_new_features.html
> {quote}The REFRESH statement now updates information about HDFS block locations. Therefore, you can perform a fast and efficient REFRESH after doing an HDFS rebalancing operation instead of the more expensive INVALIDATE METADATA statement.
> {quote}
> However there is no change in HDFS or Impala side to support this. There may be some misunderstanding. After hdfs load balancing, user still needs to run INVALIDATE METADATA <table> to get latest block metadata.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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