[jira] [Updated] (HIVE-11567) Some trace logs seeped through with new log4j2 changes
[ https://issues.apache.org/jira/browse/HIVE-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Shelukhin updated HIVE-11567: +1 Some trace logs seeped through with new log4j2 changes -- Key: HIVE-11567 URL: https://issues.apache.org/jira/browse/HIVE-11567 Project: Hive Issue Type: Sub-task Components: Logging Affects Versions: 2.0.0 Reporter: Prasanth Jayachandran Assignee: Prasanth Jayachandran Fix For: 2.0.0 Attachments: HIVE-11567.patch Observed hive.log file size difference when running with new log4j2 changes (HIVE-11304). Looks like the default threshold was DEBUG in log4j1.x (as log4j.threshold was misspelt). In log4j2 the default threshold was set to ALL which emitted some trace logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-11567) Some trace logs seeped through with new log4j2 changes
[ https://issues.apache.org/jira/browse/HIVE-11567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prasanth Jayachandran updated HIVE-11567: - Attachment: HIVE-11567.patch Some trace logs seeped through with new log4j2 changes -- Key: HIVE-11567 URL: https://issues.apache.org/jira/browse/HIVE-11567 Project: Hive Issue Type: Sub-task Components: Logging Affects Versions: 2.0.0 Reporter: Prasanth Jayachandran Assignee: Prasanth Jayachandran Fix For: 2.0.0 Attachments: HIVE-11567.patch Observed hive.log file size difference when running with new log4j2 changes (HIVE-11304). Looks like the default threshold was DEBUG in log4j1.x (as log4j.threshold was misspelt). In log4j2 the default threshold was set to ALL which emitted some trace logs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
