Hi, I'm having trouble updating jar files containing udf's.  In my testing,
I often find that I need to change a udf but when I redeploy a jar for it, I
can't seem to get pig to acknowledge the new code (I get the same error as
before despite knowing the stack trace couldn't have come from the new
code).

I tried some of the obvious things like "sh rm <jar file>", restarting pig,
and re-registering the jar but none of them seem to work.

Is there a way to update jars like this without having to constantly change
the names of the functions (my current hacky workaround)?

Restarting pig should work. In fact, I've gotten new code loaded up by
simply re-registering the (updated) jar.
There must be something wonky going on with your paths and/or jarring
processes.

D

On Wed, Oct 5, 2011 at 6:00 PM, Eric Czech <[EMAIL PROTECTED]> wrote:

> Hi, I'm having trouble updating jar files containing udf's.  In my testing,
> I often find that I need to change a udf but when I redeploy a jar for it,
> I
> can't seem to get pig to acknowledge the new code (I get the same error as
> before despite knowing the stack trace couldn't have come from the new
> code).
>
> I tried some of the obvious things like "sh rm <jar file>", restarting pig,
> and re-registering the jar but none of them seem to work.
>
> Is there a way to update jars like this without having to constantly change
> the names of the functions (my current hacky workaround)?
>

what do you mean by 'redeploy a jar'?

only place where the jar is mentioned is in 'register' statement, right? in
that case, restarting pig should certainly work.

Raghu.
On Wed, Oct 5, 2011 at 6:00 PM, Eric Czech <[EMAIL PROTECTED]> wrote:

> Hi, I'm having trouble updating jar files containing udf's.  In my testing,
> I often find that I need to change a udf but when I redeploy a jar for it,
> I
> can't seem to get pig to acknowledge the new code (I get the same error as
> before despite knowing the stack trace couldn't have come from the new
> code).
>
> I tried some of the obvious things like "sh rm <jar file>", restarting pig,
> and re-registering the jar but none of them seem to work.
>
> Is there a way to update jars like this without having to constantly change
> the names of the functions (my current hacky workaround)?
>