[
https://issues.apache.org/jira/browse/TRAFODION-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945388#comment-14945388
]
ASF GitHub Bot commented on TRAFODION-25:
-----------------------------------------
Github user DaveBirdsall commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/102#discussion_r41293809
--- Diff: core/sql/optimizer/BindRelExpr.cpp ---
@@ -11046,6 +11046,14 @@ RelExpr *MergeDelete::bindNode(BindWA *bindWA)
bindWA->setErrStatus();
return this;
}
+ if (CmpCommon::getDefault(COMP_BOOL_175) == DF_OFF)
--- End diff --
UPDATE + INSERT does not have the issue; I saw successful TSJ plans with
UPDATE + INSERT. With DELETE + INSERT, the TSJ plans fail. DELETE + INSERT was
turned off by default before; only by turning on COMP_BOOL_175 to ON would it
be allowed. I took this to mean that it was known to be buggy, and left it in
this state. I spent about a half day debugging it without success and abandoned
that effort for now as it seemed outside the scope of the costing work. I will
file a JIRA.
> 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)
