[jira] [Updated] (PIG-4430) Pig should support reading log4j.properties file from classpath as well

["Ratandeep Ratti (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PIG-4430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ratandeep Ratti updated PIG-4430:
---------------------------------
    Attachment: log4j.patch

Attaching the patch

> Pig should support reading log4j.properties file from classpath as well
> -----------------------------------------------------------------------
>
>                 Key: PIG-4430
>                 URL: https://issues.apache.org/jira/browse/PIG-4430
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Ratandeep Ratti
>         Attachments: log4j.patch
>
>
> Currently, we can specify a log4j.properties file to Pig command line like so
> {noformat}
> pig -4 /path/to/log4j.properties
> {noformat}
> It will be quite helpful if it read the log4j.properties from the classpath as well.
> For instance in the same command we can specify...
> {noformat}
> pig -4 log4j.properties
> {noformat}
> And Pig can first try to read it as a file and failing that could try reading it from the classpath, similar to how log4j handles the property - log4j.configuration.
> We needed this as one of your projects contained  the log4j.properties file  embedded inside the project jar
> I've attached a simple patch with a testcase to that effect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)