Re: Error while parsing commandline properties

2013-03-02 Thread Jeff Yuan
I guess maybe I was confused between the concept of parameter (as in parameter substitution) and properties. I think I cleared it up now. Thanks! On Fri, Mar 1, 2013 at 5:21 PM, Johnny Zhang wrote: > Hi, Jeff: > If I understand correctly. I think you need that if you need to pass value > to param

Re: Error while parsing commandline properties

2013-03-01 Thread Johnny Zhang
Hi, Jeff: If I understand correctly. I think you need that if you need to pass value to parameter in pig script in runtime. However, the value should be passed in by "pig -param =" instead of "pig -p", Can you try that? Johnny On Fri, Mar 1, 2013 at 4:58 PM, Jeff Yuan wrote: > Hi Johnny, > A

Re: Error while parsing commandline properties

2013-03-01 Thread Jeff Yuan
Hi Johnny, Actually it was a mistake on my part. I was writing some custom code that launches Grunt and I had a call that passed my input through ParameterSubstitutionPreprocessor when it may not need to be. I haven't had a chance to thoroughly read that class. Do you know off the top of your head

Re: Error while parsing commandline properties

2013-03-01 Thread Johnny Zhang
Hi, Jeff: It works for me though. Can you paste the whole command? Johnny On Fri, Mar 1, 2013 at 4:04 PM, Jeff Yuan wrote: > Hi guys, > > I'm running pig from the command line in local mode, and trying to > pass in some properties, for example: > pig -x local ... -p mapred.map.tasks=2 -p mapre

Error while parsing commandline properties

2013-03-01 Thread Jeff Yuan
Hi guys, I'm running pig from the command line in local mode, and trying to pass in some properties, for example: pig -x local ... -p mapred.map.tasks=2 -p mapred.reduce.tasks=1 ... I'm getting errors; INFO parameters.ParameterSubstitutionPreprocessor: Encountered " ".map.tasks=2 "" at line 1, c