Alan Gates a écrit :
It is already possible to do the following:
PigContext context = new PigContext(execType); // execType is
PigServer.ExecType
PigServer pig = new PigServer(context);
pig.registerQuery(...);
...
PigContext contains, among other things, a Properties object that keep
the properties. What's missing is a way to set values in that
properties object. So if we added a setProperty() method to
PigContext I think we'd have what you suggest below.
Yes I think that would provide more flexibility (at least for me :-) )
btw I have a question about using Properties class. May be I missed the
reason but java.util.Map is more generic and would allow to change
internal implementation easily doing someting like:
Map props = new Properties();
public Map getProperties(){}
public void setProperties(Map props){}
my 2 cents
