[jira] [Updated] (PIG-2034) Pig client uses fs.default.name as provided from the JobTracker instead of local value

["Bill Graham (JIRA)" <ji...@apache.org>]

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

Bill Graham updated PIG-2034:
-----------------------------

    Attachment: pig_1304465896181.log

Attached is an error log that shows what the exception looks like when the servers {{fs.default.name}} can't be resolved by the client when running from the pig shell.

The script that produced this was this:

{code}
raw = LOAD '/user/bob/some_file.txt' AS (a, b, c, d);
A = LIMIT raw 10;
dump A;
{code}

> Pig client uses fs.default.name as provided from the JobTracker instead of local value
> --------------------------------------------------------------------------------------
>
>                 Key: PIG-2034
>                 URL: https://issues.apache.org/jira/browse/PIG-2034
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Bill Graham
>         Attachments: pig_1304465896181.log
>
>
> When submitting a Pig job, the client uses the {{fs.default.name}} supplied to it by the JobTracker (via core-site.xml on the master typically) during the staging phase. After that, the client then uses the {{fs.default.name}} from it's local configs. This seems like a bug to me. Expected behavior would be to always use the local value.
> I found this bug when the server configs were set to not use a FQDN for {{fs.default.name}}. This caused the client to fail because it didn't have the same default DNS domain. 

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