[jira] [Updated] (HIVE-25001) Improvement for some debug-logging guards
[ https://issues.apache.org/jira/browse/HIVE-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-25001: Description: Moving some potential expensive statements (e.g. `Arrays.toString`) into the adjacent logging guards, since these statements are merely used by the following logging calls. Note that the fix in `LlapTaskSchedulerService.java` is different with other cases in this patch, because the variable `requestedHostsDebugStr` is used by several debug-logging calls, and we have to declare and assign the variable before these debug-logging calls. was:Moving some potential expensive statements (e.g. `Arrays.toString`) into the adjacent logging guards, since these statements are merely used by the following logging calls. > Improvement for some debug-logging guards > - > > Key: HIVE-25001 > URL: https://issues.apache.org/jira/browse/HIVE-25001 > Project: Hive > Issue Type: Improvement >Reporter: Chen Zhi >Priority: Minor > Attachments: HIVE-25001.patch > > > Moving some potential expensive statements (e.g. `Arrays.toString`) into the > adjacent logging guards, since these statements are merely used by the > following logging calls. > Note that the fix in `LlapTaskSchedulerService.java` is different with other > cases in this patch, because the variable `requestedHostsDebugStr` is used by > several debug-logging calls, and we have to declare and assign the variable > before these debug-logging calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25001) Improvement for some debug-logging guards
[ https://issues.apache.org/jira/browse/HIVE-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-25001: Description: Moving some potential expensive statements (e.g. `Arrays.toString()`) into the adjacent logging guards, since these statements are merely used by the following logging calls. (was: Moving some potential expensive statements into the adjacent logging guards, since these statements are merely used by the following logging calls.) > Improvement for some debug-logging guards > - > > Key: HIVE-25001 > URL: https://issues.apache.org/jira/browse/HIVE-25001 > Project: Hive > Issue Type: Improvement >Reporter: Chen Zhi >Priority: Minor > Attachments: HIVE-25001.patch > > > Moving some potential expensive statements (e.g. `Arrays.toString()`) into > the adjacent logging guards, since these statements are merely used by the > following logging calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25001) Improvement for some debug-logging guards
[ https://issues.apache.org/jira/browse/HIVE-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-25001: Description: Moving some potential expensive statements (e.g. `Arrays.toString`) into the adjacent logging guards, since these statements are merely used by the following logging calls. (was: Moving some potential expensive statements (e.g. `Arrays.toString()`) into the adjacent logging guards, since these statements are merely used by the following logging calls.) > Improvement for some debug-logging guards > - > > Key: HIVE-25001 > URL: https://issues.apache.org/jira/browse/HIVE-25001 > Project: Hive > Issue Type: Improvement >Reporter: Chen Zhi >Priority: Minor > Attachments: HIVE-25001.patch > > > Moving some potential expensive statements (e.g. `Arrays.toString`) into the > adjacent logging guards, since these statements are merely used by the > following logging calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-25001) Improvement for some debug-logging guards
[ https://issues.apache.org/jira/browse/HIVE-25001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-25001: Attachment: HIVE-25001.patch > Improvement for some debug-logging guards > - > > Key: HIVE-25001 > URL: https://issues.apache.org/jira/browse/HIVE-25001 > Project: Hive > Issue Type: Improvement >Reporter: Chen Zhi >Priority: Minor > Attachments: HIVE-25001.patch > > > Moving some potential expensive statements into the adjacent logging guards, > since these statements are merely used by the following logging calls. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.08.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.04.patch, HIVE-21392.05.patch, HIVE-21392.06.patch, > HIVE-21392.07.patch, HIVE-21392.08.patch, HIVE-21392.patch > > Time Spent: 1h 20m > 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=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)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[
https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Zhi updated HIVE-21556:
Labels: patch-available (was: )
> Useless configuration for old jetty in log4j.properties
> ---
>
> Key: HIVE-21556
> URL: https://issues.apache.org/jira/browse/HIVE-21556
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
>Reporter: Chen Zhi
>Priority: Minor
> Labels: patch-available
> Attachments: HIVE-21556.1.patch
>
>
>
> {code:java}
> logger.Mortbay.name = org.mortbay
> logger.Mortbay.level = INFO
> {code}
> The logger `Mortbay` in log4j.properties is used to control logging
> activities of jetty (6.x). However, we have upgrade to jetty 9 in HIVE-16049,
> the package name has changed to `org.eclipse.jetty` and we have added the new
> logger to control jetty. `Mortbay` is useless. I guess we can remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[
https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Zhi updated HIVE-21556:
Attachment: HIVE-21556.1.patch
> Useless configuration for old jetty in log4j.properties
> ---
>
> Key: HIVE-21556
> URL: https://issues.apache.org/jira/browse/HIVE-21556
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
>Reporter: Chen Zhi
>Priority: Minor
> Attachments: HIVE-21556.1.patch
>
>
>
> {code:java}
> logger.Mortbay.name = org.mortbay
> logger.Mortbay.level = INFO
> {code}
> The logger `Mortbay` in log4j.properties is used to control logging
> activities of jetty (6.x). However, we have upgrade to jetty 9 in HIVE-16049,
> the package name has changed to `org.eclipse.jetty` and we have added the new
> logger to control jetty. `Mortbay` is useless. I guess we can remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[
https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Zhi updated HIVE-21556:
Description:
{code:java}
logger.Mortbay.name = org.mortbay
logger.Mortbay.level = INFO
{code}
The logger `Mortbay` in log4j.properties is used to control logging activities
of jetty (6.x). However, we have upgrade to jetty 9 in HIVE-16049, the package
name has changed to `org.eclipse.jetty` and we have added the new logger to
control jetty. `Mortbay` is useless. I guess we can remove it.
was:
{{The logger `Mortbay`}}
{code:java}
// code placeholder
{code}
{{in log4j.properties is used to control logging activities of jetty (6.x).
However, we have upgrade to jetty 9 in HIVE-16049, the package name has changed
to `org.eclipse.jetty` and we have added `Jetty` logger to control the new
version. `Mortbay` is useless. I guess we can remove it.}}
> Useless configuration for old jetty in log4j.properties
> ---
>
> Key: HIVE-21556
> URL: https://issues.apache.org/jira/browse/HIVE-21556
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
>Reporter: Chen Zhi
>Priority: Minor
>
>
> {code:java}
> logger.Mortbay.name = org.mortbay
> logger.Mortbay.level = INFO
> {code}
> The logger `Mortbay` in log4j.properties is used to control logging
> activities of jetty (6.x). However, we have upgrade to jetty 9 in HIVE-16049,
> the package name has changed to `org.eclipse.jetty` and we have added the new
> logger to control jetty. `Mortbay` is useless. I guess we can remove it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[
https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chen Zhi updated HIVE-21556:
Description:
{{The logger `Mortbay`}}
{code:java}
// code placeholder
{code}
{{in log4j.properties is used to control logging activities of jetty (6.x).
However, we have upgrade to jetty 9 in HIVE-16049, the package name has changed
to `org.eclipse.jetty` and we have added `Jetty` logger to control the new
version. `Mortbay` is useless. I guess we can remove it.}}
was:The configuration `org.mortbay` in log4j.properties is used to control
logging activities of jetty (6.x). However, we have upgrade to jetty 9 in
HIVE-16049, the package name has changed to `org.eclipse.jetty`. This
configuration is useless. I guess we can remove it.
> Useless configuration for old jetty in log4j.properties
> ---
>
> Key: HIVE-21556
> URL: https://issues.apache.org/jira/browse/HIVE-21556
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
>Reporter: Chen Zhi
>Priority: Minor
>
> {{The logger `Mortbay`}}
> {code:java}
> // code placeholder
> {code}
> {{in log4j.properties is used to control logging activities of jetty (6.x).
> However, we have upgrade to jetty 9 in HIVE-16049, the package name has
> changed to `org.eclipse.jetty` and we have added `Jetty` logger to control
> the new version. `Mortbay` is useless. I guess we can remove it.}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21556: Description: The configuration `org.mortbay` in log4j.properties is used to control logging activities of jetty (6.x). However, we have upgrade to jetty 9 in HIVE-16049, the package name has changed to `org.eclipse.jetty`. This configuration is useless. I guess we can remove it. (was: The configuration `org.mortbay` in log4j.properties is used to control logging activities of jetty . However, we have upgrade to jetty 9 in HIVE-16049, the package name has changed to `org.eclipse.jetty`, this configuration is useless. I guess we can remove it.) > Useless configuration for old jetty in log4j.properties > --- > > Key: HIVE-21556 > URL: https://issues.apache.org/jira/browse/HIVE-21556 > Project: Hive > Issue Type: Improvement > Components: Configuration >Reporter: Chen Zhi >Priority: Minor > > The configuration `org.mortbay` in log4j.properties is used to control > logging activities of jetty (6.x). However, we have upgrade to jetty 9 in > HIVE-16049, the package name has changed to `org.eclipse.jetty`. This > configuration is useless. I guess we can remove it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21556: Description: The configuration `org.mortbay` in log4j.properties is used to control logging activities of jetty . However, we have upgrade to jetty 9 in HIVE-16049, the package name has changed to `org.eclipse.jetty`, this configuration is useless. I guess we can remove it. (was: We has upgrade to jetty 9 in HIVE-16049, the configuration `org.mortbay` in log4j.properties for old version of jetty is useless. ) > Useless configuration for old jetty in log4j.properties > --- > > Key: HIVE-21556 > URL: https://issues.apache.org/jira/browse/HIVE-21556 > Project: Hive > Issue Type: Improvement > Components: Configuration >Reporter: Chen Zhi >Priority: Minor > > The configuration `org.mortbay` in log4j.properties is used to control > logging activities of jetty . However, we have upgrade to jetty 9 in > HIVE-16049, the package name has changed to `org.eclipse.jetty`, this > configuration is useless. I guess we can remove it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21556) Useless configuration for old jetty in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21556: Description: We has upgrade to jetty 9 in HIVE-16049, the configuration `org.mortbay` in log4j.properties for old version of jetty is useless. (was: We has upgrade to jetty 9 in [HIVE-16049](https://issues.apache.org/jira/browse/HIVE-16049), the configuration `org.mortbay` in log4j.properties for old version of jetty is useless. ) > Useless configuration for old jetty in log4j.properties > --- > > Key: HIVE-21556 > URL: https://issues.apache.org/jira/browse/HIVE-21556 > Project: Hive > Issue Type: Improvement > Components: Configuration >Reporter: Chen Zhi >Priority: Minor > > We has upgrade to jetty 9 in HIVE-16049, the configuration `org.mortbay` in > log4j.properties for old version of jetty is useless. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.07.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.04.patch, HIVE-21392.05.patch, HIVE-21392.06.patch, > HIVE-21392.07.patch, HIVE-21392.patch > > Time Spent: 1h 20m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.06.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.04.patch, HIVE-21392.05.patch, HIVE-21392.06.patch, > HIVE-21392.patch > > Time Spent: 1h 20m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.05.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.04.patch, HIVE-21392.05.patch, HIVE-21392.patch > > Time Spent: 1h 20m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.04.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.04.patch, HIVE-21392.patch > > Time Spent: 1h 20m > 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=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)
[jira] [Commented] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793287#comment-16793287 ] Chen Zhi commented on HIVE-21392: - Finally, figure out the reason for test failure. I edit the patch in windows and the EOL has been changed. > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.patch > > Time Spent: 50m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.03.patch > 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.02.patch, HIVE-21392.03.patch, > HIVE-21392.patch > > Time Spent: 50m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.02.patch > 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.02.patch, HIVE-21392.patch > > Time Spent: 50m > 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=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)
[jira] [Updated] (HIVE-21392) Misconfigurations of DataNucleus log in log4j.properties
[ https://issues.apache.org/jira/browse/HIVE-21392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Zhi updated HIVE-21392: Attachment: HIVE-21392.patch > 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 > Attachments: HIVE-21392.patch > > > 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=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)
