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.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()

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

Reply via email to