You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2011/04/25 23:09:03 UTC

[jira] [Resolved] (PIG-1865) BinStorage/PigStorageSchema cannot load data from a different namenode

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

Daniel Dai resolved PIG-1865.
-----------------------------

      Resolution: Fixed
    Hadoop Flags: [Reviewed]

Patch committed to both trunk and 0.9 branch.

> BinStorage/PigStorageSchema cannot load data from a different namenode
> ----------------------------------------------------------------------
>
>                 Key: PIG-1865
>                 URL: https://issues.apache.org/jira/browse/PIG-1865
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.7.0, 0.8.0, 0.9.0
>            Reporter: Vivek Padmanabhan
>            Assignee: Daniel Dai
>             Fix For: 0.9.0
>
>         Attachments: PIG-1865-1.patch
>
>
> BinStorage/PigStorageSchema cannot load data from a different namenode. The main reason for this is that, in the getSchema method , they use org.apache.pig.impl.io.FileLocalizer to check whether the exists, but the filesystem in HDataStorage refers to the natively configured dfs.
> The test case is simple :
> a = load 'hdfs://<nn2>/input' using BinStorage();
> dump a;
> Here if I specify -Dmapreduce.job.hdfs-servers, it should have worked , by pig still takes the fs from fs.default.name so to make it work i had to override  fs.default.name in pig command line.
> Raising this as a bug since the same scenario works with PigStorage.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira