Putting the jars on your classpath works as long as the classes you
need are directly referenced in your script. So:
B = foreach A generate com.mycompany.myudf($0);
If myudf is in a jar somewhere in your classpath then it will be
picked up. If myudf depends on the class myudfsupport which is also
in a jar on your classpath, myudfsupport will not be picked up. It
must be explicitly registered.
Alan.
On Feb 5, 2010, at 11:36 AM, Zaki Rahaman wrote:
I've never tried this but putting te jars on your pig classpath
should save you from having to register as I believe pig looks here
for jars by default
Sent from my iPhone
On Feb 5, 2010, at 1:58 PM, Chris Riccomini
<[email protected]> wrote:
What I want to do is register the jar WITHOUT register. That is,
when I
issue my pig commandline call to start pig, it will register it at
that
point rather than in my pig script.
This will save our users from all having to register 3 or 4 jars
that they
always will need to use pig effectively on our Hadoop cluster.
Thanks,
Chris
On 2/5/10 10:46 AM, "Ashutosh Chauhan" <[email protected]>
wrote:
'register' is your friend here
http://hadoop.apache.org/pig/docs/r0.5.0/piglatin_reference.html#REGISTER
Ashutosh
On Thu, Feb 4, 2010 at 23:25, Chris Riccomini <[email protected]
> wrote:
Hi All,
We have a use-case where we want to automatically register
certain jars for
command-line users. I tried using –jar, but this switch seems to do
absolutely nothing.
How do we go about auto-registering jars using pig? Any help is
much
appreciated.
Thanks in advance!
Chris
