This is an automated email from the ASF dual-hosted git repository. stigahuang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/impala.git
commit d853fab8499ae8368e5f963f646ab516fe2ee577 Author: jasonmfehr <[email protected]> AuthorDate: Wed Mar 5 15:53:20 2025 -0800 IMPALA-13837: Fix Misspelling and Remove S3Guard from Docs This patch fixes a small mis-spelling and also removes references to S3Guard since it is no longer recommended now that AWS S3 has strong consistency. Changes were verified by successfully running 'make' from the 'docs' directory. Change-Id: Ibea7e6ba20dcdb48c410e1ad46de3749b68e8d25 Reviewed-on: http://gerrit.cloudera.org:8080/22585 Reviewed-by: Impala Public Jenkins <[email protected]> Tested-by: Impala Public Jenkins <[email protected]> --- docs/topics/impala_data_cache.xml | 2 +- docs/topics/impala_s3.xml | 4 ---- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/topics/impala_data_cache.xml b/docs/topics/impala_data_cache.xml index 9c18635e9..ec5278438 100644 --- a/docs/topics/impala_data_cache.xml +++ b/docs/topics/impala_data_cache.xml @@ -84,7 +84,7 @@ under the License. <p> In Impala 3.4 and higher, you can configure one of the following cache eviction policies for the data cache: <ul> <li>LRU (Least Recently Used--the default)</li> - <li>LIRS (Inter-referenece Recency Set)</li> + <li>LIRS (Inter-reference Recency Set)</li> </ul> LIRS is a scan-resistent, low performance-overhead policy. You configure a cache eviction policy using the <codeph>--data_cache_eviction_policy</codeph> Impala Daemon start-up flag: </p> diff --git a/docs/topics/impala_s3.xml b/docs/topics/impala_s3.xml index 4fa507bd2..37e81aff2 100644 --- a/docs/topics/impala_s3.xml +++ b/docs/topics/impala_s3.xml @@ -119,10 +119,6 @@ under the License. </li> <li>Enable <xref href="impala_data_cache.xml#data_cache">data cache for remote reads</xref>.</li> - <li>Enable <xref - href="https://hadoop.apache.org/docs/current/hadoop-aws/tools/hadoop-aws/s3guard.html"; - format="html" scope="external">S3Guard</xref> in your cluster for - data consistency.</li> <li> <p> Too many files in a table can make metadata load and update slow in S3. If too many requests are made to S3, S3 has a back-off
