Hello,
In pig script of pig-0.8.1, I did not find command line for adding pig*.jar into CLASSPATH environment variable. Just the following:
# during development pig jar might be in build
for f in $PIG_HOME/build/pig-*-SNAPSHOT.jar; do
    CLASSPATH=${CLASSPATH}:$f;
done

Should I add some commands in pig script for adding pig*.jar into CLASSPATH? If no need, please tell your opinion. Thank you.

for f in $PIG_HOME/pig-*-core.jar; do
    CLASSPATH=${CLASSPATH}:$f;
done

In release tall ball, you will have pig-0.8.1-core.jar, that's the jar pig
script use.

Daniel

2011/9/9 lulynn_2008 <[EMAIL PROTECTED]>

>  Hello,
> In pig script of pig-0.8.1, I did not find command line for adding pig*.jar
> into CLASSPATH environment variable. Just the following:
> # during development pig jar might be in build
> for f in $PIG_HOME/build/pig-*-SNAPSHOT.jar; do
>    CLASSPATH=${CLASSPATH}:$f;
> done
>
> Should I add some commands in pig script for adding pig*.jar into
> CLASSPATH? If no need, please tell your opinion. Thank you.
>

Daniel, thank you for your quick response.
I think pig-0.8.1-*.jar should always be added into classpath. Is this correct?
At 2011-09-11 08:58:15,"Daniel Dai" <[EMAIL PROTECTED]> wrote:
>for f in $PIG_HOME/pig-*-core.jar; do
>    CLASSPATH=${CLASSPATH}:$f;
>done
>
>In release tall ball, you will have pig-0.8.1-core.jar, that's the jar pig
>script use.
>
>Daniel
>
>2011/9/9 lulynn_2008 <[EMAIL PROTECTED]>
>
>>  Hello,
>> In pig script of pig-0.8.1, I did not find command line for adding pig*.jar
>> into CLASSPATH environment variable. Just the following:
>> # during development pig jar might be in build
>> for f in $PIG_HOME/build/pig-*-SNAPSHOT.jar; do
>>    CLASSPATH=${CLASSPATH}:$f;
>> done
>>
>> Should I add some commands in pig script for adding pig*.jar into
>> CLASSPATH? If no need, please tell your opinion. Thank you.
>>