[
https://issues.apache.org/jira/browse/PIG-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12862087#action_12862087
]
Daniel Dai commented on PIG-1381:
---------------------------------
For option 3, yes, we need to move key value pair to xml. I checked current
pig.properties, seems moving all properties is straightforward. Option 2 and 3
are functionally equivalent. The advantage for 2 is simplicity. The advantage
for 3 is more hadoop compliant, one work with hadoop will be clear what
pig-default.xml and pig-site-xml means.
> 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.
