ation?
Thanks in advance!
*
*
*
*
*Pig Stack Trace*
*---*
*ERROR 6017: Execution failed, while processing
hdfs://tasktracker:5/tmp/temp1581022765/tmp939224290,
hdfs://tasktracker:5/tmp/temp1581022765/tmp-1028111033,
hdfs://tasktracker:5/tmp/temp1581022765/tmp-198156265,
any idea about how
> to debug this? I don't even know which step of my 500 line pig script caused
> this error.
>
> Any suggestions on how to track down the offending operation?
>
> Thanks in advance!
> *
> *
> *
> *
> *Pig Stack Trace*
> *---*
&
>> this error.
>>
>> Any suggestions on how to track down the offending operation?
>>
>> Thanks in advance!
>> *
>> *
>> *
>> *
>> *Pig Stack Trace*
>> *---*
>> *ERROR 6017: Execution failed, while processing
>> hdfs:/
On Mar 12, 2010, at 10:36 AM, hc busy wrote:
Is there any work towards something like C languages '#include' in
Pig? My
large pig script is actually developed separately in several smaller
pig
files. Individually the pig files do not run because they depend on
previous
scripts, but logi
Alan, this would be quite useful, as essentially this would allow developers
to create functions by writing them into separate pig scripts and combining
them as necessary.
For example we have code that auto-generates load statements with fairly
complex schemas based on protocol buffers (see
http:/
In your example below how would the results of these load functions be
accessed in your main script?
I certainly see the value of #include plus functions (or #define if
you prefer). Without functions though you'll have namespace clashes
(any relation names used in the imported files will b
Alan -- yeah, right now we use the rather brittle approach of naming
conventions to do this. Something more template/macro-like would be better.
Of course something like Piglet, or equivalents in other languages, can
obviate the need for these constructs, and I am not entirely sure functions,
loops
IMO Pig would do best to stay a data flow language and not take on
control flow. (I'm not sure all committers agree with me on this.)
There's no lack of scripting languages out there that can be used for
that (as seen on PIG-928) or frameworks like Piglet or Oozie. But we
could still do
ahhh, that %declare a(...) is exactly what would help with the variable name
problem. Because otherwise, it's like a register language where all
function.pig files take parameters named a1,a2,a3,a4,a5,... and before
#include'ing a pig file, the caller sets a1, a2, a3, a4,...; and
function.pig will
Okay, Alan, I went back and read PIG-928, which is great!
The example
%declare a(x, y, k1, k2) join x by k1, y by k2
is nice, but maybe a little more extensive. Because I need something like
>declare template(table1, table2, fieldName1, fieldName2, const1, const2){
temp = filter table1 by fi
10 matches
Mail list logo
