[
https://issues.apache.org/jira/browse/TRAFODION-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944957#comment-14944957
]
ASF GitHub Bot commented on TRAFODION-25:
-----------------------------------------
Github user nonstop-qfchen commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/102#discussion_r41257544
--- Diff: core/sql/optimizer/OptPhysRelExpr.cpp ---
@@ -16546,6 +16546,18 @@ RelInternalSP::costMethod() const
} // RelInternalSP::costMethod()
//<pb>
+CostMethod *
+HbaseDelete::costMethod() const
+{
+ if (CmpCommon::getDefault(HBASE_DELETE_COSTING) == DF_OFF)
+ return RelExpr::costMethod(); // returns cost 1 cost object
--- End diff --
maybe say "returns the default cost method that returns an object of cost
1".
> Insert, delete and update operators should use specialized cost method
> -----------------------------------------------------------------------
>
> Key: TRAFODION-25
> URL: https://issues.apache.org/jira/browse/TRAFODION-25
> Project: Apache Trafodion
> Issue Type: Bug
> Reporter: Qifan Chen
> Assignee: David Wayne Birdsall
> Labels: performance
>
> In Trafodion, insert, delete and update operators do not use a specialized
> cost method that model the true operation involved.
> As a result, these operators can be assigned a zero cost and the query plan
> may not be optimal. In one example, a delete query against a partitioned
> table may get a serial plan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
