You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ning Zhang (JIRA)" <ji...@apache.org> on 2010/12/20 21:53:01 UTC
[jira] Created: (HIVE-1855) Include Process ID in the log4j log
file name
Include Process ID in the log4j log file name
---------------------------------------------
Key: HIVE-1855
URL: https://issues.apache.org/jira/browse/HIVE-1855
Project: Hive
Issue Type: Improvement
Reporter: Ning Zhang
Assignee: Ning Zhang
Attachments: HIVE-1855.patch
Hive client side always log into /tmp/${user.name}/hive.log. If there are multipel CLI running on the same host, logging could be stopped or if it is not it's difficult to distinguish messages between them. It would be easier for debugging if different CLI output to different log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1855) Include Process ID in the log4j log
file name
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1855:
-----------------------------
Status: Patch Available (was: Open)
> Include Process ID in the log4j log file name
> ---------------------------------------------
>
> Key: HIVE-1855
> URL: https://issues.apache.org/jira/browse/HIVE-1855
> Project: Hive
> Issue Type: Improvement
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Attachments: HIVE-1855.patch
>
>
> Hive client side always log into /tmp/${user.name}/hive.log. If there are multipel CLI running on the same host, logging could be stopped or if it is not it's difficult to distinguish messages between them. It would be easier for debugging if different CLI output to different log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1855) Include Process ID in the log4j log
file name
Posted by "Ning Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-1855:
-----------------------------
Attachment: HIVE-1855.patch
> Include Process ID in the log4j log file name
> ---------------------------------------------
>
> Key: HIVE-1855
> URL: https://issues.apache.org/jira/browse/HIVE-1855
> Project: Hive
> Issue Type: Improvement
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Attachments: HIVE-1855.patch
>
>
> Hive client side always log into /tmp/${user.name}/hive.log. If there are multipel CLI running on the same host, logging could be stopped or if it is not it's difficult to distinguish messages between them. It would be easier for debugging if different CLI output to different log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HIVE-1855) Include Process ID in the log4j log
file name
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973383#action_12973383 ]
Namit Jain commented on HIVE-1855:
----------------------------------
+1
> Include Process ID in the log4j log file name
> ---------------------------------------------
>
> Key: HIVE-1855
> URL: https://issues.apache.org/jira/browse/HIVE-1855
> Project: Hive
> Issue Type: Improvement
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Attachments: HIVE-1855.patch
>
>
> Hive client side always log into /tmp/${user.name}/hive.log. If there are multipel CLI running on the same host, logging could be stopped or if it is not it's difficult to distinguish messages between them. It would be easier for debugging if different CLI output to different log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HIVE-1855) Include Process ID in the log4j log
file name
Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Namit Jain updated HIVE-1855:
-----------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Committed. Thanks Ning
> Include Process ID in the log4j log file name
> ---------------------------------------------
>
> Key: HIVE-1855
> URL: https://issues.apache.org/jira/browse/HIVE-1855
> Project: Hive
> Issue Type: Improvement
> Reporter: Ning Zhang
> Assignee: Ning Zhang
> Attachments: HIVE-1855.patch
>
>
> Hive client side always log into /tmp/${user.name}/hive.log. If there are multipel CLI running on the same host, logging could be stopped or if it is not it's difficult to distinguish messages between them. It would be easier for debugging if different CLI output to different log files.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.