hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olga Natkovich (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-1004) FINDBUGS: CN_IDIOM_NO_SUPER_CALL in org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators
Date Fri, 09 Oct 2009 20:05:32 GMT

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

Olga Natkovich updated PIG-1004:
--------------------------------

    Description: 
Will address this during next cleanup:

CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.PODistinct.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLimit.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrange.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrangeForIllustrate.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POOptimizedForEach.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POSort.clone()
does not call super.clone()

  was:
Will address this during next cleanup:

CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.plans.PhysicalPlan.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.PODistinct.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLimit.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrange.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrangeForIllustrate.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POOptimizedForEach.clone()
does not call super.clone()
CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POSort.clone()
does not call super.clone()


> FINDBUGS: CN_IDIOM_NO_SUPER_CALL in 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-1004
>                 URL: https://issues.apache.org/jira/browse/PIG-1004
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Olga Natkovich
>
> Will address this during next cleanup:
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.PODistinct.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POForEach.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLimit.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrange.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POLocalRearrangeForIllustrate.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POOptimizedForEach.clone()
does not call super.clone()
> CN 	org.apache.pig.backend.hadoop.executionengine.physicalLayer.relationalOperators.POSort.clone()
does not call super.clone()

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message