Or /path{1,2}/{01,02,03,08,09,10,11,12}/*/data/ ?
Its bad practice to do the above, but should do the job.
On 3/20/13 4:25 PM, "Johnny Zhang" wrote:
>do you use PigStorage ? Can you try -param input='/path1/{08,09,10,11,12}/
>*/data/,/path2/{01,02,03}/*/data/' ?
>
>Johnny Zhang
>
>
>On Wed, Mar
do you use PigStorage ? Can you try -param input='/path1/{08,09,10,11,12}/
*/data/,/path2/{01,02,03}/*/data/' ?
Johnny Zhang
On Wed, Mar 20, 2013 at 4:14 PM, Tim Chan wrote:
> I'm using parameter passing to pass an input path to my pig script.
>
> This does not seem to work:
>
> -param input=/
I like the new feature of IMPORT, it allows me to break up big chunks of
code into manageable, reusable units.
but one issue is that if I get a compile error or run time error in one of
the macros being IMPORTed, pig shows the error line to be where the macro
is used, not the actual code in the ma
I'm using parameter passing to pass an input path to my pig script.
This does not seem to work:
-param input=/path1/{08,09,10,11,12}/*/data/,/path2/{01,02,03}/*/data/
Is there an interface to get the standard out and standard error
streams for a pig execution? I'm using the Java interface and directly
calling PigServer.executeBatch() for example and getting back
List. The ExecJob interface has some interface for getSTDOut
and getSTDError, but any calls to these
Nice summarization Koji. Wish we had some object that has byte[] and length
instead of byte[] as the return type of serialize() and method param of
deserialize(). That would enable reuse and cut down on some of the copy.
At least there is one copy we can cut down without any API changes by
having
Hi.
Do you know anyone using custom serializer/deserializer in pig streaming?
I was looking at http://wiki.apache.org/pig/PigStreamingFunctionalSpec and was
impressed on various features it supports.
Then, looking at the code, I was sad to see many additional data copying done
to support those
