Chris Ge created IMPALA-13935:
---------------------------------
Summary: The log level of the front-end Java program and the log
level of the back-end C++ program cannot be associated, causinng confusion.
Key: IMPALA-13935
URL: https://issues.apache.org/jira/browse/IMPALA-13935
Project: IMPALA
Issue Type: Improvement
Components: Infrastructure
Affects Versions: Not Applicable
Reporter: Chris Ge
Impala wrapped the Frontend embedded java program logs into the backend GLOG
infrasture.
But For java program, we have TRACE, DEBUG, LOG, WARN,ERROR, FATAL log levels,
but C++ program, we have only INFO, WARNING, ERROR and FATAL.
So whenever we enabled the TRACE level log for java program, the corresponding
log level will be translated to the Backend INFO level. for example
this is a debug level log in the FE:
[https://github.com/apache/impala/blob/master/fe/src/main/java/org/apache/impala/rewrite/ConvertToCNFRule.java#L102]
But it will be converted to INFO level in the impalad log
*I0326* 06:38:22.734169 108511 ConvertToCNFRule.java:100]
344220716d8a3dbf:9fdd1f5800000000] It is not feasible to rewrite predicate
We can see lots of such examples, that is confusing, and Hope we can have some
mechanism to distinguish those java TRACE/DEBUG/WARN/ERROR log messages even
they are converted to the log form of BE
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
