You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Ashutosh Chauhan (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/25 09:28:39 UTC

[jira] [Resolved] (PIG-2383) Pig launcher script would benefit from exec'ing hadoop instead of java (in cases where Hadoop is available)

     [ https://issues.apache.org/jira/browse/PIG-2383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashutosh Chauhan resolved PIG-2383.
-----------------------------------

       Resolution: Duplicate
    Fix Version/s: 0.9.1

Dup of PIG-2239
                
> Pig launcher script would benefit from exec'ing hadoop instead of java (in cases where Hadoop is available)
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-2383
>                 URL: https://issues.apache.org/jira/browse/PIG-2383
>             Project: Pig
>          Issue Type: Improvement
>          Components: grunt
>    Affects Versions: 0.8.0, 0.8.1, 0.9.0
>            Reporter: Roman Shaposhnik
>            Priority: Minor
>             Fix For: 0.9.1
>
>
> It seems that pig launcher script needs to replicate a lot of hadoop launcher script functionality if it wants to set things like java library path and classpath just right. Currently users are burdened with the need to do it manually even when all the appropriate setting are available for Hadoop. For instance, in order for the following to succeed, Pig has to be explicitly told about lzo libs (PIG_OPTS="$PIG_OPTS -Djava.library.path=..path..to.hadoop..native..libs"
> {noformat}
> E = LOAD 'foo.txt.lzo' USING PigStorage() as (a:int);
> DUMP E;
> {noformat}
> The suggestion is to follow the trend set by Hive and use hadoop launcher script instead of Java. If the Hadoop launcher script is not available we can alway fall back on the default behavior.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira