lmhmhl commented on a change in pull request #9019:
URL: https://github.com/apache/shardingsphere/pull/9019#discussion_r557145116
##########
File path:
shardingsphere-jdbc/shardingsphere-jdbc-core/src/main/java/org/apache/shardingsphere/driver/jdbc/core/statement/ShardingSphereStatement.java
##########
@@ -385,7 +390,11 @@ protected Boolean getSaneResult(final SQLStatement
sqlStatement) {
};
return driverJDBCExecutor.execute(executionGroups, sqlStatement,
routeUnits, jdbcExecutorCallback);
}
-
+
+ private void isToCalcite(final boolean isToCalcite) {
Review comment:
> Hi, we can not add `set` or `get` functions for tests. I guess you
want to make this property `true`. That way, please refer to the following
steps,
>
> * Add another single table to `config-calcite.yaml`
> * Modify your test SQL as `select xx,xx from singleTable1, singleTable2
where singleTable1.xx=singleTable2 and xx`
> * If necessary, you can add SQLS to prepare the Calcite UT in
`jdbc_data.sql` and `jdbc_init.sql`. It is straightforward to create tables to
do calcite tests, isn't it?
@tristaZero, Thanks for your encouragement, you are so kind. I have a
questions, how to go the branch as follows when test？It seems nowhere can set
the boolean value `toCalcite` in `RouteContext`.
```
if (executionContext.getRouteContext().isToCalcite()) {
return executeQueryByCalcite();
}
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
