[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Resolution: Fixed Fix Version/s: 0.4.0 Status: Resolved (was: Patch Available) I don't have a unit test case for the same reason of the first patch. See my first comment. > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: duplicate_message.patch, PIG-882-1.patch, > PIG-882-2.patch, PIG-882-3.patch, PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: duplicate_message.patch Previous patch introduce a duplicate error message problem. The cause of the problem is that we set the org.apache.pig to use appender PIGCONSOLE, but do not change the root logger. Log4j think that root logger is using a default appender and org.apache.pig is using PIGCONSOLE. So the message is printed out twice to the default appender and PIGCONSOLE. > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: duplicate_message.patch, PIG-882-1.patch, > PIG-882-2.patch, PIG-882-3.patch, PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Status: Patch Available (was: Reopened) > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: duplicate_message.patch, PIG-882-1.patch, > PIG-882-2.patch, PIG-882-3.patch, PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Resolution: Fixed Status: Resolved (was: Patch Available) All unit tests passed. Hudson do not respond, committed patch anyway. > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Status: Patch Available (was: Open) Pick me up, Hudson! > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Status: Open (was: Patch Available) > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Fix Version/s: 0.4.0 Affects Version/s: 0.3.0 Status: Patch Available (was: In Progress) > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Affects Versions: 0.3.0 >Reporter: Thejas M Nair >Assignee: Daniel Dai > Fix For: 0.4.0 > > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: PIG-882-5.patch > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Status: In Progress (was: Patch Available) > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch, PIG-882-5.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: PIG-882-4.patch Sync with latest trunk > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch, > PIG-882-4.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: PIG-882-3.patch Modify patch according to Santhosh's suggestion. > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch, PIG-882-3.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Status: Patch Available (was: Open) > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: PIG-882-2.patch New patch propagates pig log level to backend. I do not find a good way to write a unit test especially for the backend part so no unit test was added, > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch, PIG-882-2.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (PIG-882) log level not propogated to loggers
[ https://issues.apache.org/jira/browse/PIG-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Dai updated PIG-882: --- Attachment: PIG-882-1.patch > log level not propogated to loggers > > > Key: PIG-882 > URL: https://issues.apache.org/jira/browse/PIG-882 > Project: Pig > Issue Type: Bug > Components: impl >Reporter: Thejas M Nair > Attachments: PIG-882-1.patch > > > Pig accepts log level as a parameter. But the log level it captures is not > set appropriately, so that loggers in different classes log at the specified > level. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
