[ 
https://issues.apache.org/jira/browse/PIG-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229901#comment-13229901
 ] 

Julien Le Dem commented on PIG-2573:
------------------------------------

ant test-patch

    [exec] -1 overall.  
    [exec] 
    [exec]     +1 @author.  The patch does not contain any @author tags.
    [exec] 
    [exec]     +1 tests included.  The patch appears to include 5 new or 
modified tests.
    [exec] 
    [exec]     -1 javadoc.  The javadoc tool appears to have generated 1 
warning messages.
    [exec] 
    [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
    [exec] 
    [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
warnings.
    [exec] 
    [exec]     -1 release audit.  The applied patch generated 541 release audit 
warnings (more than the trunk's current 534 warnings).

the new warnings are unrelated to this patch.

+1 on my side 
                
> Automagically setting parallelism based on input file size does not work with 
> HCatalog
> --------------------------------------------------------------------------------------
>
>                 Key: PIG-2573
>                 URL: https://issues.apache.org/jira/browse/PIG-2573
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Travis Crawford
>            Assignee: Travis Crawford
>         Attachments: PIG-2573_get_size_from_stats_if_possible.diff, 
> PIG-2573_get_size_from_stats_if_possible_2.diff, 
> PIG-2573_get_size_from_stats_if_possible_3.diff, 
> PIG-2573_get_size_from_stats_if_possible_4.diff, 
> PIG-2573_move_getinputbytes_to_loadfunc.diff
>
>
> PIG-2334 was helpful in understanding this issue. Short version is input file 
> size is only computed if the path begins with a whitelisted prefix, currently:
> * /
> * hdfs:
> * file:
> * s3n:
> As HCatalog locations use the form {{dbname.tablename}} the input file size 
> is not computed, and the size-based parallelism optimization breaks.
> DETAILS:
> I discovered this issue comparing two runs on the same script, one loading 
> regular HDFS paths, and one with HCatalog db.table names. I just happened to 
> notice the "Setting number of reducers" line difference.
> {code:title=Loading HDFS files reducers is set to 99}
> 2012-03-08 01:33:56,522 [main] INFO  
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler
>  - BytesPerReducer=1000000000 maxReducers=999 totalInputFileSize=98406674162
> 2012-03-08 01:33:56,522 [main] INFO  
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler
>  - Neither PARALLEL nor default parallelism is set for this job. Setting 
> number of reducers to 99
> {code}
> {code:title=Loading with an HCatalog db.table name}
> 2012-03-08 01:06:02,283 [main] INFO  
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler
>  - BytesPerReducer=1000000000 maxReducers=999 totalInputFileSize=0
> 2012-03-08 01:06:02,283 [main] INFO  
> org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.JobControlCompiler
>  - Neither PARALLEL nor default parallelism is set for this job. Setting 
> number of reducers to 1
> {code}
> Possible fix: Pig should just ask the loader for the size of its inputs 
> rather than special-casing certain location types.

--
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

        

Reply via email to