hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.V.Chaitanya Krishna (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-1381) Need a way for Pig to take an alternative property file
Date Thu, 29 Apr 2010 02:28:49 GMT

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

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

bq.  I think key=value is easier for people to understand.

 Yes. I think it is a valid way of putting up properties. But I think xml format gives more
structured-ness to the properties file, no? But however, this would also mean a significant
code change in terms of the approach for loading the properties (things like xml parsing etc.
might have to be taken care of).

bq.  For option 2 I think we'd need to provide an empty pig.properties file (just as hadoop
provides an empty hadoop-site.xml).

  We can provide the current pig.properties file itself, with the default values. So it would
be somewhat analogous to hadoop-default.xml. I would also propose that this be bundled in
the jar itself and thus avoid it to be changed by users. (because they would have a different
properties file already to put up their settings).

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.


Mime
View raw message