[
https://issues.apache.org/jira/browse/TRAFODION-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944923#comment-14944923
]
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_r41255397
--- Diff: core/sql/generator/GenPreCode.cpp ---
@@ -11180,13 +11179,33 @@ NABoolean
HbaseAccess::isHbaseFilterPred(Generator * generator, ItemExpr * ie,
else if (ie->getOperatorType() == ITM_NOT_EQUAL)
op = "NOT_EQUAL";
else if (ie->getOperatorType() == ITM_LESS)
- op = "LESS";
+ {
+ if (flipOp)
+ op = "GREATER";
+ else
+ op = "LESS";
+ }
else if (ie->getOperatorType() == ITM_LESS_EQ)
- op = "LESS_OR_EQUAL";
+ {
+ if (flipOp)
+ op = "GREATER_OR_EQUAL";
+ else
+ op = "LESS_OR_EQUAL";
--- End diff --
should be "LESS".
> 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)
