[
https://issues.apache.org/jira/browse/IMPALA-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500475#comment-16500475
]
ASF subversion and git services commented on IMPALA-6020:
---------------------------------------------------------
Commit c2186c752727316bdfca8879b6124c37a650530d in impala's branch
refs/heads/2.x from [~arodoni_cloudera]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=c2186c7 ]
IMPALA-6020: [DOCS] REFRESH statement cannot detect HDFS block movement
Change-Id: Ib6de1469e0f375511fd415e79074f4ec72cf109b
Reviewed-on: http://gerrit.cloudera.org:8080/10470
Reviewed-by: Bharath Vissapragada <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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: [email protected]
For additional commands, e-mail: [email protected]
