[GitHub] [shardingsphere] tristaZero commented on issue #8284: [New feature] Federated SQL query and Query optimization are going to sail out.

[GitBox <gi...@apache.org>]

tristaZero commented on issue #8284:
URL: https://github.com/apache/shardingsphere/issues/8284#issuecomment-753959592


   @guimingyue @junwen12221 @Aaaaaaron ,
   
   Hi guys,
   
   Currently, the query optimization module has been plugging into  ShardingSphere (From parse to execute). However, it is just like a `fridge`. That is, we need to put more valuable `food`(SqlNode transformation, planner, Interpretable) to it. The related classes are `SqlNodeConverter`, `PlannerInitializer`, `CalciteRawExecutor` waiting to be implemented.
   Especially, I want to listen your opinion how to get a `resultSet` if we use `Interpretable` of `Calcite` in `CalciteRawExecutor` (I have no idea about `resultSetMetadata`). Why do we need to get a `resultSet`? The reason is that we have to return `QueryResult` from `CalciteRawExecutor` to dock with the executor of ShardingSphere (Refer to `CalciteJDBCExecutor`).
   
   @guimingyue, do you have any plan for `SqlNodeConverter`, `PlannerInitializer`?
   @Aaaaaaron @junwen12221  I am unsure whether you still want to join in this feature (`CalciteRawExecutor` needs your attention).


----------------------------------------------------------------
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:
users@infra.apache.org