hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gonglinglei (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19403) Demote 'Pattern' Logging
Date Mon, 07 May 2018 03:20:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-19403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

gonglinglei updated HIVE-19403:
-------------------------------
    Attachment: HIVE-19403.1.patch

> Demote 'Pattern' Logging
> ------------------------
>
>                 Key: HIVE-19403
>                 URL: https://issues.apache.org/jira/browse/HIVE-19403
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>    Affects Versions: 3.0.0, 2.4.0
>            Reporter: BELUGA BEHR
>            Assignee: gonglinglei
>            Priority: Trivial
>              Labels: noob
>         Attachments: HIVE-19403.1.patch
>
>
> In the {{DDLTask}} class, there is some logging that is not helpful to a cluster admin
and should be demoted to _debug_ level logging.  In fact, in one place in the code, it already
is.
> {code}
> LOG.info("pattern: {}", showDatabasesDesc.getPattern());
> LOG.debug("pattern: {}", pattern);
> LOG.info("pattern: {}", showFuncs.getPattern());
> LOG.info("pattern: {}", showTblStatus.getPattern());
> {code}
> Here is an example... as an admin, I can already see what the pattern is, I do not need
this extra logging.  It provides no additional context.
> {code:java|title=Example}
> 2018-05-03 03:08:26,354 INFO  org.apache.hadoop.hive.ql.Driver: [HiveServer2-Background-Pool:
Thread-101980]: Executing command(queryId=hive_20180503030808_e53c26ef-2280-4eca-929b-668503105e2e):
SHOW TABLE EXTENDED FROM my_db LIKE '*'
> 2018-05-03 03:08:26,355 INFO  hive.ql.exec.DDLTask: [HiveServer2-Background-Pool: Thread-101980]:
pattern: *
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message