You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/05 09:39:00 UTC
[jira] [Work logged] (HIVE-21392) Misconfigurations of DataNucleus
log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?focusedWorklogId=207710&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-207710 ]
ASF GitHub Bot logged work on HIVE-21392:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Mar/19 09:38
Start Date: 05/Mar/19 09:38
Worklog Time Spent: 10m
Work Description: coder-chenzhi commented on pull request #556: HIVE-21392 Fix misconfigurations of DataNucleus log in log4j.properties
URL: https://github.com/apache/hive/pull/556
HIVE-21392 Misconfigurations of DataNucleus log in log4j.properties
In the patch of [HIVE-12020](https://issues.apache.org/jira/browse/HIVE-12020), we changed the DataNucleus related logging configuration from nine fine-grained loggers with three coarse-grained loggers (DataNucleus, Datastore and JPOX).
As Prasanth Jayachandran [explain](https://issues.apache.org/jira/browse/HIVE-12020?focusedCommentId=15025612&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15025612), these three loggers are the top-level logger in DataNucleus, so that we don't need to specify other loggers for DataNucleus.
However, according to the [documents](http://www.datanucleus.org/products/accessplatform/logging.html) and [source codes](https://github.com/datanucleus/datanucleus-core/blob/master/src/main/java/org/datanucleus/util/NucleusLogger.java#L108) of DataNucleus, the top-level logger in DataNucleus is `DataNucleus`. Therefore, we just need to keep the right one.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 207710)
Time Spent: 10m
Remaining Estimate: 0h
> Misconfigurations of DataNucleus log in log4j.properties
> --------------------------------------------------------
>
> Key: HIVE-21392
> URL: https://issues.apache.org/jira/browse/HIVE-21392
> Project: Hive
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 2.0.0
> Reporter: Chen Zhi
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-21392.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the patch of [HIVE-12020|https://issues.apache.org/jira/browse/HIVE-12020], we changed the DataNucleus related logging configuration from nine fine-grained loggers with three coarse-grained loggers (DataNucleus, Datastore and JPOX). As Prasanth Jayachandran [explain|https://issues.apache.org/jira/browse/HIVE-12020?focusedCommentId=15025612&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15025612], these three loggers are the top-level logger in DataNucleus, so that we don't need to specify other loggers for DataNucleus. However, according to the [documents|http://www.datanucleus.org/products/accessplatform/logging.html] and [source codes|https://github.com/datanucleus/datanucleus-core/blob/master/src/main/java/org/datanucleus/util/NucleusLogger.java#L108] of DataNucleus, the top-level logger in DataNucleus is `DataNucleus`. Therefore, we just need to keep the right one.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)