You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Bill Graham (JIRA)" <ji...@apache.org> on 2012/08/13 03:36:40 UTC
[jira] [Created] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Bill Graham created PIG-2870:
--------------------------------
Summary: pigServer.openIterator fails for jobs with no input splits
Key: PIG-2870
URL: https://issues.apache.org/jira/browse/PIG-2870
Project: Pig
Issue Type: Bug
Affects Versions: 0.11
Reporter: Bill Graham
Assignee: Bill Graham
Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433636#comment-13433636 ]
Dmitriy V. Ryaboy commented on PIG-2870:
----------------------------------------
I don't think it's as simple as reverting PIG-2578. Things get dicey when multiple output formats / store funcs go modifying a single shared JobConf, but the solution in PIG-2578 was clearly flawed. Just reverting it will still leave us in a bad state.. we need to change the whole interaction so that StoreFuncs can modify Configurations as needed, but don't stomp all over each other.
In case of PIG-2821, what happens if you need to store to multiple HBase clusters? The 2 instances will clobber each other, won't they?
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440911#comment-13440911 ]
Dmitriy V. Ryaboy commented on PIG-2870:
----------------------------------------
Reverted PIG-2578. Is there still a no-input-split problem, or does this solve the issue?
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Rohini Palaniswamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433473#comment-13433473 ]
Rohini Palaniswamy commented on PIG-2870:
-----------------------------------------
We should revert PIG-2578.
https://issues.apache.org/jira/browse/PIG-2821?focusedCommentId=13433397&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13433397
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Updated] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated PIG-2870:
-----------------------------
Status: Patch Available (was: Open)
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433697#comment-13433697 ]
Bill Graham commented on PIG-2870:
----------------------------------
There are at least two use cases that need to be met as I see it:
1. A user needs to set a field on the Config object that will be seen when the MR job(s) run. Care must be taken that one instance doesn't clobber the other with two different setting. We could wrap the conf object and throw an exception or log a warning in this case.
2. Multiple instances of store StoreFuncs need to be initialized differently and pass the state from the client StoreFunc to their respective server StoreFunc. This seems like UDFContext should be used in this case (and fixed as needed if it doesn't work currently).
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Updated] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated PIG-2870:
-----------------------------
Attachment: PIG-2870.1.patch
Here's a unit test and a patch.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Raghu Angadi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438926#comment-13438926 ]
Raghu Angadi commented on PIG-2870:
-----------------------------------
+1 for reverting PIG-2578. As Rohini pointed out it was essentially a workaround for a HCat issue. It made things worse.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Updated] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham updated PIG-2870:
-----------------------------
Status: Open (was: Patch Available)
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432881#comment-13432881 ]
Bill Graham commented on PIG-2870:
----------------------------------
FYI, this is what the exception looks like:
{noformat}
org.apache.pig.impl.logicalLayer.FrontendException: ERROR 1066: Unable to open iterator for alias T2
at org.apache.pig.PigServer.openIterator(PigServer.java:836)
at xxxx.TestIndexing.testEmptySearch(TestIndexing.java:283)
Caused by: org.apache.pig.backend.executionengine.ExecException: ERROR 2088: Unable to get results for: file:/tmp/temp1703266029/tmp911072373:org.apache.pig.impl.io.InterStorage
at org.apache.pig.backend.hadoop.executionengine.HJob.getResults(HJob.java:99)
at org.apache.pig.PigServer.openIterator(PigServer.java:818)
Caused by: org.apache.hadoop.mapreduce.lib.input.InvalidInputException: Input path does not exist: file:/tmp/temp1703266029/tmp911072373
at org.apache.hadoop.mapreduce.lib.input.FileInputFormat.listStatus(FileInputFormat.java:231)
at org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.PigFileInputFormat.listStatus(PigFileInputFormat.java:37)
at org.apache.hadoop.mapreduce.lib.input.FileInputFormat.getSplits(FileInputFormat.java:248)
at org.apache.pig.impl.io.ReadToEndLoader.init(ReadToEndLoader.java:158)
at org.apache.pig.impl.io.ReadToEndLoader.<init>(ReadToEndLoader.java:120)
at org.apache.pig.backend.hadoop.executionengine.HJob.getResults(HJob.java:92)
{noformat}
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Rohini Palaniswamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433929#comment-13433929 ]
Rohini Palaniswamy commented on PIG-2870:
-----------------------------------------
Correction: so that issues like PIG-2870 don't occur.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Dmitriy V. Ryaboy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433319#comment-13433319 ]
Dmitriy V. Ryaboy commented on PIG-2870:
----------------------------------------
There seems to be something systemic at play here, which is only partially worked around by the proposed patch. Let's think through what's going on here some more.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Commented] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Rohini Palaniswamy (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433927#comment-13433927 ]
Rohini Palaniswamy commented on PIG-2870:
-----------------------------------------
bq. In case of PIG-2821, what happens if you need to store to multiple HBase clusters? The 2 instances will clobber each other, won't they?
Currently i don't think it is possible to store to multiple clusters because of the way hbase-site.xml is picked from classpath. Will need an option to specify the conf location as part of HBaseStorage for that I guess. But storing to multiple tables in hbase cluster should work as HBaseStorage keeps a local copy of Configuration and uses it along with UDFContext Properties. Anyways planning to rework PIG-2821 to store hbase properties in UDFContext instead of JobConf. Also found that the credentials are getting added to the JobConf when PigOutputFormat.checkOutputSpecs calls setStoreLocation when I was tring to figure out how HCatStorer was working with secure hcat even with PIG-2578. Ideally that is not how it should be working, but at least credentials are getting passed to the job someway. So I can getaway without reverting PIG-2578 for PIG-2821. But I am concerned about other StoreFunc implementations and Dmitriy's statement that "many StoreFunc implementations that rely on being able to mess with the JobConf"
bq. I don't think it's as simple as reverting PIG-2578.
Agree, we need to fix it correctly. We did some work on being able to use multiple output formats without one stepping on each other to write to multiple hcat tables at once by playing with the configuration and merging.
http://svn.apache.org/viewvc/incubator/hcatalog/branches/branch-0.4/src/java/org/apache/hcatalog/mapreduce/MultiOutputFormat.java?revision=1351510&view=markup
Something like that in pig would help. Simpler thing in pig's case would be to have a wrapper and serialize non-JT settings to one UDFContext property and merge JT specific configs like DistributedCache settings and set it in the job. And in backend, copy settings from UDFContext back into the job passed to setStoreLocation.
bq. I am aware of many StoreFunc implementations that rely on being able to mess with the JobConf. This is an undocumented and backwards incompatible change. (Dmitriy's comment from PIG-2578)
Agreeing to a design and fixing this correctly with backward compatibility might take some time. Was just thinking of getting PIG-2578 reverted till we get the fix done, so that atleast we have the old behaviour so that issues like PIG-2780 don't occur. It would be difficult to track down and go through all user written StoreFunc's and ensure none of them have done a set on JobConf. We have a release with PIG-2578 only out for 1.5 months and no issues have been reported so far. But the pig-0.10 adoption is only at 30-40% and many might not have downloaded the new release. What worries me is that there could be silent failures or wrong outputs depending upon the implementation of the StoreFunc.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
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
[jira] [Resolved] (PIG-2870) pigServer.openIterator fails for jobs
with no input splits
Posted by "Bill Graham (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bill Graham resolved PIG-2870.
------------------------------
Resolution: Duplicate
Thanks Dmitriy, PIG-2578 fixed this issue. Marking as duplicate.
> pigServer.openIterator fails for jobs with no input splits
> ----------------------------------------------------------
>
> Key: PIG-2870
> URL: https://issues.apache.org/jira/browse/PIG-2870
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.11
> Reporter: Bill Graham
> Assignee: Bill Graham
> Attachments: PIG-2870.1.patch
>
>
> Jobs that have valid input data, but 0 input splits (this is the case where indexing implemented in the {{InputFormat}} might return 0 splits for an aggressive filter) fail when {{pigServer.openIterator}} is called. This is because {{mapred.output.dir}} isn't set, so the job succeeds without creating the empty output directory. The {{ReadToEndLoader}} then fails due to the null input directory.
> It seems PIG-2578 introduced this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira