You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Olga Natkovich (JIRA)" <ji...@apache.org> on 2009/10/09 21:45:31 UTC
[jira] Commented: (PIG-1003) FINDBUGS: CN_IDIOM_NO_SUPER_CALL in
org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators
[ https://issues.apache.org/jira/browse/PIG-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12764170#action_12764170 ]
Olga Natkovich commented on PIG-1003:
-------------------------------------
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.Divide.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.EqualToExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.GreaterThanExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.GTOrEqualToExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.LessThanExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.LTOrEqualToExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.Mod.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.Multiply.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.NotEqualToExpr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POAnd.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POBinCond.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POCast.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POIsNull.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POMapLookUp.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PONegative.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PONot.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POOr.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POProject.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORegexp.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.PORelationToExprProject.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POUserComparisonFunc.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.POUserFunc.clone() does not call super.clone()
CN org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators.Subtract.clone() does not call super.clone()
> FINDBUGS: CN_IDIOM_NO_SUPER_CALL in org.apache.pig.backend.hadoop.executionengine.physicalLayer.expressionOperators
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PIG-1003
> URL: https://issues.apache.org/jira/browse/PIG-1003
> Project: Pig
> Issue Type: Bug
> Reporter: Olga Natkovich
>
> All physical expression operators have this issue. In the clone method, they instanciate a new object rather than call super.clone.
> This is a major change and for now I am planning to exclude this warning. We will address it once we work on the frontend rewrite.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.