[impala] 05/06: Logging current database context when logging analyzing queries.

[lv...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

lv pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git

commit 113b2eb120ca36777b5f33632deb3a5dcfe3322a
Author: Philip Zeyliger <ph...@cloudera.com>
AuthorDate: Thu Dec 27 14:47:53 2018 -0800

    Logging current database context when logging analyzing queries.
    
    The "analyzing query" log message is a reliable way to correlate
    queries with ther thread ids, but the session database name
    is missing there. Adding it in.
    
    Change-Id: I70886be4685e0d3ae7ca9f6e57e8159dc39c67c7
    Reviewed-on: http://gerrit.cloudera.org:8080/12301
    Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
    Tested-by: Impala Public Jenkins <im...@cloudera.com>
---
 fe/src/main/java/org/apache/impala/service/Frontend.java | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/fe/src/main/java/org/apache/impala/service/Frontend.java b/fe/src/main/java/org/apache/impala/service/Frontend.java
index 2e61472..5d0ae61 100644
--- a/fe/src/main/java/org/apache/impala/service/Frontend.java
+++ b/fe/src/main/java/org/apache/impala/service/Frontend.java
@@ -1248,7 +1248,8 @@ public class Frontend {
   private TExecRequest getTExecRequest(PlanCtx planCtx, EventSequence timeline)
       throws ImpalaException {
     TQueryCtx queryCtx = planCtx.getQueryContext();
-    LOG.info("Analyzing query: " + queryCtx.client_request.stmt);
+    LOG.info("Analyzing query: " + queryCtx.client_request.stmt + " db: "
+        + queryCtx.session.database);
 
     int attempt = 0;
     String retryMsg = "";