[
https://issues.apache.org/jira/browse/TRAFODION-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944919#comment-14944919
]
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_r41255210
--- Diff: core/sql/generator/GenPreCode.cpp ---
@@ -4385,12 +4377,14 @@ RelExpr * GenericUpdate::preCodeGen(Generator *
generator,
GenExit();
}
- if ((getOperatorType() == REL_HBASE_DELETE) &&
+ if ((getOperatorType() != REL_HBASE_UPDATE) &&
(mergeInsertRecExpr().entries() > 0) &&
(CmpCommon::getDefault(COMP_BOOL_175) == DF_OFF))
{
+ // MERGE with INSERT is limited to HBase updates unless
+ // the CQD is on
*CmpCommon::diags() << DgSqlCode(-3241)
- << DgString0(" MERGE delete not allowed with
INSERT.");
+ << DgString0(" This MERGE is not allowed with
INSERT.");
--- End diff --
Maybe reword the error message to "This MERGE with DELETE is not allowed
with INSERT on non-Trafodion tables".
> 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)
