You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ga...@apache.org on 2019/03/19 09:46:31 UTC
[impala] 09/11: [DOCS] Event based HMS sync works for Metadata V1
and V2
This is an automated email from the ASF dual-hosted git repository.
gaborkaszab pushed a commit to branch branch-3.2.0
in repository https://gitbox.apache.org/repos/asf/impala.git
commit 8e0228fa327e954edb68343943e8dc967c0bd957
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Wed Mar 13 14:32:41 2019 -0700
[DOCS] Event based HMS sync works for Metadata V1 and V2
- Move the Metadata V2 note so that it does not apply to event based
sync.
Change-Id: I366add1016d8dad876f100a0b27ba3051e2cafbb
Reviewed-on: http://gerrit.cloudera.org:8080/12745
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Vihang Karajgaonkar <vi...@cloudera.com>
Reviewed-by: Bharath Vissapragada <bh...@cloudera.com>
---
docs/topics/impala_metadata.xml | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/docs/topics/impala_metadata.xml b/docs/topics/impala_metadata.xml
index dc5a658..7caa00e 100644
--- a/docs/topics/impala_metadata.xml
+++ b/docs/topics/impala_metadata.xml
@@ -34,9 +34,8 @@ under the License.
<conbody>
<p>
- This topic describes various knobs in Impala to tune how Impala manages its metadata.
- Before you use the features in this topic, you need to turn on Metadata V2 in your
- cluster.
+ This topic describes various knobs for controlling how Impala manages its metadata to
+ improve overall performance and scalability.
</p>
<p outputclass="toc inpage"/>
@@ -111,7 +110,7 @@ under the License.
<li>
Incremental stats will not be replicated to <codeph>impalad</codeph> and will be
accessed on demand from <codeph>catalogd</codeph>, resulting in a reduced memory
- footprint of impalad.
+ footprint of <codeph>impalad</codeph>.
</li>
</ul>