You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ta...@apache.org on 2019/11/01 20:53:56 UTC
[impala] 01/02: IMPALA-8768: [DOCS] Added conditions for queries
recorded in audit log
This is an automated email from the ASF dual-hosted git repository.
tarmstrong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git
commit 49a31aef0b71e94cbbea412a4071721b3b5f5359
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Tue Oct 29 14:40:56 2019 -0700
IMPALA-8768: [DOCS] Added conditions for queries recorded in audit log
Change-Id: I809e716e66558db02e6401bd218b3dd2de49864c
Reviewed-on: http://gerrit.cloudera.org:8080/14575
Tested-by: Impala Public Jenkins <im...@cloudera.com>
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
---
docs/topics/impala_auditing.xml | 46 +++++++++++++++++------------------------
1 file changed, 19 insertions(+), 27 deletions(-)
diff --git a/docs/topics/impala_auditing.xml b/docs/topics/impala_auditing.xml
index 87307c0..8183cce 100644
--- a/docs/topics/impala_auditing.xml
+++ b/docs/topics/impala_auditing.xml
@@ -258,37 +258,29 @@ Here is an excerpt from a sample audit log file:
<conbody>
- <p>
- The kinds of SQL queries represented in the audit log are:
- </p>
+ <p> The following types of SQL operations are recorded in the audit
+ log:</p>
<ul>
- <li>
- Queries that are prevented due to lack of authorization.
- </li>
-
- <li>
- Queries that Impala can analyze and parse to determine that they are authorized. The
- audit data is recorded immediately after Impala finishes its analysis, before the
- query is actually executed.
- </li>
+ <li> Queries that are prevented due to lack of authorization. </li>
+ <li> Queries that Impala can analyze and parse to determine that they
+ are authorized. The audit data is recorded immediately after Impala
+ finishes its analysis, before the query is actually executed. </li>
+ <li> Queries whose results are available to be fetched by clients.</li>
+ <li>Finished DDL operations.</li>
</ul>
- <p>
- The audit log does not contain entries for queries that could not be parsed and
- analyzed. For example, a query that fails due to a syntax error is not recorded in the
- audit log. The audit log also does not contain queries that fail due to a reference to a
- table that does not exist, if you would be authorized to access the table if it did
- exist.
- </p>
-
- <p>
- Certain statements in the <cmdname>impala-shell</cmdname> interpreter, such as
- <codeph>CONNECT</codeph>, <codeph rev="1.4.0">SUMMARY</codeph>,
- <codeph>PROFILE</codeph>, <codeph>SET</codeph>, and <codeph>QUIT</codeph>, do not
- correspond to actual SQL queries, and these statements are not reflected in the audit
- log.
- </p>
+ <p> The audit log does not contain entries for queries that could not be
+ parsed and analyzed. For example, a query that fails due to a syntax
+ error is not recorded in the audit log. </p>
+ <p>The audit log does not contain queries that fail due to a reference to
+ a table that does not exist. </p>
+
+ <p> Certain statements in the <cmdname>impala-shell</cmdname> interpreter,
+ such as <codeph>CONNECT</codeph>, <codeph rev="1.4.0">SUMMARY</codeph>,
+ <codeph>PROFILE</codeph>, <codeph>SET</codeph>, and
+ <codeph>QUIT</codeph>, do not correspond to actual SQL queries, and
+ these statements are not recorded in the audit log. </p>
</conbody>