David Ciemiewicz commented on PIG-602:

This sounds a lot like shell script environment variables.
As such maybe it should follow the same rich level of operations and semantics 
that you get with environment variables.

How is PigConf different from "set" properties in Pig?
Why can't both use the same mechanism?
Should they use the same mechanism?

Can / should this same mechanism let my UDFs "know" when Pig is in local mode 
versus hdfs mode? [JIRA PIG-756] (or should something different be used?

When in grunt, how can I inspect what the current PigConf values are? (Useful 
for logging and debugging)

By what mechanism can I set or override these values from within my Pig script?
Can I set the values to be one thing at one point in the Pig script and change 
it later to a new value in the Pig script?

> Pass global configurations to UDF
> ---------------------------------
>                 Key: PIG-602
>                 URL: https://issues.apache.org/jira/browse/PIG-602
>             Project: Pig
>          Issue Type: New Feature
>          Components: impl
>            Reporter: Yiping Han
>            Assignee: Alan Gates
> We are seeking an easy way to pass a large number of global configurations to 
> UDFs.
> Since our application contains many pig jobs, and has a large number of 
> configurations. Passing configurations through command line is not an ideal 
> way (i.e. modifying single parameter needs to change multiple command lines). 
> And to put everything into the hadoop conf is not an ideal way either.
> We would like to see if Pig can provide such a facility that allows us to 
> pass a configuration file in some format(XML?) and then make it available 
> through out all the UDFs.

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

Reply via email to