Hello,
First of all thank you all, I really appreciate the help I get here :)
I've now written some UDFs and did some successful local runs.
When copying the date to HDFS and trying to run my pig file I get the job fails.
Looking at the jobtracker I have the following error several times:
Job
Can you share your loader code?
On Thu, Mar 3, 2011 at 6:08 AM, Lai Will l...@student.ethz.ch wrote:
Hello,
First of all thank you all, I really appreciate the help I get here :)
I've now written some UDFs and did some successful local runs.
When copying the date to HDFS and trying to run
Yep, all you have to do is upgrade to Pig 8...
This sort of thing is one of the reasons Load/Store interfaces were
completely redesigned after Pig 0.6.
On Wed, Mar 2, 2011 at 8:46 PM, Kris Coward k...@melon.org wrote:
Yep. That did it. Now if you don't mind my asking, is there any way to
Please find it attached.
-Original Message-
From: Dmitriy Ryaboy [mailto:dvrya...@gmail.com]
Sent: Thursday, March 03, 2011 7:58 PM
To: user@pig.apache.org
Subject: Re: PigOutputFormat cannot be cast to OutputFormat
Can you share your loader code?
On Thu, Mar 3, 2011 at 6:08 AM, Lai
Coming from a user's perspective, I would have the following to say:
Anyone who is using Hadoop has an obvious understanding that 1.0 doesn't
really mean much if it's in use (which Pig obviously is). What 1.0 has the
potential to do for someone like me is that I may be able to go to Amazon
and
Hello,
When skimming through the API I sometimes find docs like:
Get the JobConf. This should only be called on the backend. It will return
null on the frontend.
What do they refer to as backend / frontend?
Best,
Will
Frontend is the machine you launch Pig from. This is where all
planning is done. The backend is the Hadoop cluster where your jobs
are executed.
Alan.
On Mar 3, 2011, at 2:03 PM, Lai Will wrote:
Hello,
When skimming through the API I sometimes find docs like:
Get the JobConf. This
Alan,
Here's another perspective, based on the conventions used in most of the
products I have worked on (okay, that's not a lot but some of them are
well regarded by customers).
Rather than focusing on the specific number, it is the transition which
is important tells users something. Let me
The hadoop classes used by the load/store functions probably belong to the
'slowly evolving' category. But I don't think any change is anticipated
soon. By the time it changes we might be ready for pig 2.0 !
Exactly! How do you know that no changes are anticipated? We need inputs from
the
