You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "V.V.Chaitanya Krishna (JIRA)" <ji...@apache.org> on 2010/04/23 12:43:50 UTC

[jira] Commented: (PIG-1381) Need a way for Pig to take an alternative property file

    [ https://issues.apache.org/jira/browse/PIG-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860210#action_12860210 ] 

V.V.Chaitanya Krishna commented on PIG-1381:
--------------------------------------------

bq. 2. Change the name for default pig.properties to pig-default.properties, and user can give a pig.properties to override
bq. 3. Further, can we consider to use pig-default.xml/pig-site.xml, which seems to be more natural for hadoop community. If so, we shall provide backward compatibility to also read pig.properties, pig-cluster-hadoop-site.xml.

 +1 to both the above approaches. In fact, I see that both are almost similar in the sense that user has the option to provide a set of properties in a file.

Since this is something that pig source-code provides, i think it makes sense to keep the filename (the one in which users can specify their own properties) fixed, rather than having it as a command line option.

Thoughts?

> Need a way for Pig to take an alternative property file
> -------------------------------------------------------
>
>                 Key: PIG-1381
>                 URL: https://issues.apache.org/jira/browse/PIG-1381
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>    Affects Versions: 0.7.0
>            Reporter: Daniel Dai
>             Fix For: 0.8.0
>
>
> Currently, Pig read the first ever pig.properties in CLASSPATH. Pig has a default pig.properties and if user have a different pig.properties, there will be a conflict since we can only read one. There are couple of ways to solve it:
> 1. Give a command line option for user to pass an additional property file
> 2. Change the name for default pig.properties to pig-default.properties, and user can give a pig.properties to override
> 3. Further, can we consider to use pig-default.xml/pig-site.xml, which seems to be more natural for hadoop community. If so, we shall provide backward compatibility to also read pig.properties, pig-cluster-hadoop-site.xml. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.