You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jo...@apache.org on 2020/04/28 02:21:47 UTC
[impala] branch master updated (c4ac9d2 -> afe765e)
This is an automated email from the ASF dual-hosted git repository.
joemcdonnell pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git.
from c4ac9d2 Revert "IMPALA-9648: Exclude netty and netty-all from hadoop-hdfs mvn download"
new 9615197 IMPALA-9613: [DOCS] Document the data_cache_eviction_policy
new afe765e Don't filter maven messages about banned dependencies
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
bin/mvn-quiet.sh | 3 ++-
docs/topics/impala_data_cache.xml | 11 +++++++++++
2 files changed, 13 insertions(+), 1 deletion(-)
[impala] 02/02: Don't filter maven messages about banned
dependencies
Posted by jo...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
joemcdonnell pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git
commit afe765e3bdf8facb1940f4c7620eb7f9084bcb1f
Author: Joe McDonnell <jo...@cloudera.com>
AuthorDate: Mon Apr 27 12:01:41 2020 -0700
Don't filter maven messages about banned dependencies
The frontend build uses the maven-enforcer-plugin to ban
some dependencies or require specific versions of dependencies.
The messages look like:
Found Banned Dependency: foo.bar.baz:1.2.3
These are currently filtered by bin/mvn-quiet.sh. This adds
an exception for "Found Banned" so they are not filtered.
Testing:
- Ran on a branch with a known banned dependency and verified
the output
Change-Id: I24abe59ad6bffb28ac63d014aa0ec7388ef5478f
Reviewed-on: http://gerrit.cloudera.org:8080/15820
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: David Knupp <dk...@cloudera.com>
---
bin/mvn-quiet.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/bin/mvn-quiet.sh b/bin/mvn-quiet.sh
index cc673da..f782ff4 100755
--- a/bin/mvn-quiet.sh
+++ b/bin/mvn-quiet.sh
@@ -36,7 +36,8 @@ LOGGING_OPTIONS="-Dorg.slf4j.simpleLogger.showDateTime \
# Always use maven's batch mode (-B), as it produces output that is easier to parse.
if ! mvn -B $IMPALA_MAVEN_OPTIONS $LOGGING_OPTIONS "$@" | \
- tee -a "$LOG_FILE" | grep -E -e WARNING -e ERROR -e SUCCESS -e FAILURE -e Test; then
+ tee -a "$LOG_FILE" | \
+ grep -E -e WARNING -e ERROR -e SUCCESS -e FAILURE -e Test -e "Found Banned"; then
echo "mvn $IMPALA_MAVEN_OPTIONS $@ exited with code $?"
exit 1
fi
[impala] 01/02: IMPALA-9613: [DOCS] Document the
data_cache_eviction_policy
Posted by jo...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
joemcdonnell pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git
commit 961519747bf75bc2ba8519d00757b8e176d14538
Author: Kris Hahn <kh...@cloudera.com>
AuthorDate: Wed Apr 8 20:39:00 2020 -0700
IMPALA-9613: [DOCS] Document the data_cache_eviction_policy
Describe start up flag to set LRU or LIRS policy. Tweak LIRS description.
Change-Id: Ic46ae00549157535c12f761aff7747fc90249d98
Reviewed-on: http://gerrit.cloudera.org:8080/15694
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Joe McDonnell <jo...@cloudera.com>
---
docs/topics/impala_data_cache.xml | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/docs/topics/impala_data_cache.xml b/docs/topics/impala_data_cache.xml
index fed4181..210b181 100644
--- a/docs/topics/impala_data_cache.xml
+++ b/docs/topics/impala_data_cache.xml
@@ -85,6 +85,17 @@ under the License.
<codeblock>--data_cache=/data/0,/data/1:500GB</codeblock>
+ <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>
+ </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>
+ <p>
+<codeblock>--data_cache_eviction_policy=<varname>policy</varname>
+</codeblock>
+ </p>
</conbody>
</concept>