[DOCS] Fixed misleading documentation on Impala + HDFS caching Change-Id: I63cd1ff7b885a094a4a3e91c31101d25414b4db7 Reviewed-on: http://gerrit.cloudera.org:8080/10454 Reviewed-by: Tim Armstrong <[email protected]> Tested-by: Impala Public Jenkins <[email protected]>
Project: http://git-wip-us.apache.org/repos/asf/impala/repo Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/fd27b170 Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/fd27b170 Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/fd27b170 Branch: refs/heads/2.x Commit: fd27b1708f8605e8c91396c8f6e4a657dd1b218c Parents: 86c61bc Author: Alex Rodoni <[email protected]> Authored: Fri May 18 14:32:02 2018 -0700 Committer: Impala Public Jenkins <[email protected]> Committed: Fri May 25 23:17:16 2018 +0000 ---------------------------------------------------------------------- docs/topics/impala_perf_hdfs_caching.xml | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/impala/blob/fd27b170/docs/topics/impala_perf_hdfs_caching.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_hdfs_caching.xml b/docs/topics/impala_perf_hdfs_caching.xml index e1f25a6..8f0fbb9 100644 --- a/docs/topics/impala_perf_hdfs_caching.xml +++ b/docs/topics/impala_perf_hdfs_caching.xml @@ -270,14 +270,11 @@ show table stats census; location, dropping the table, and so on. </p> - <p> - When data is requested to be pinned in memory, that process happens in the background without blocking - access to the data while the caching is in progress. Loading the data from disk could take some time. - Impala reads each HDFS data block from memory if it has been pinned already, or from disk if it has not - been pinned yet. When files are added to a table or partition whose contents are cached, Impala - automatically detects those changes and performs a <codeph>REFRESH</codeph> automatically once the relevant - data is cached. - </p> + <p> When data is requested to be pinned in memory, that process happens in + the background without blocking access to the data while the caching is + in progress. Loading the data from disk could take some time. Impala + reads each HDFS data block from memory if it has been pinned already, or + from disk if it has not been pinned yet.</p> <p> The amount of data that you can pin on each node through the HDFS caching mechanism is subject to a quota
