tristaZero commented on issue #8284: URL: https://github.com/apache/shardingsphere/issues/8284#issuecomment-757423938
Hi, community, Here is the progress update so far. ### Functions - [x] The **research** on the source code and API of Apache Calcite - [x] The **design plan** on Apache ShardingSphere and Apache Calcite - [x] The implementation of `CalciteLogicSchemaFactory`, `CalciteLogicSchema`, and `CalciteFilterableTable` - [x] The Calcite JDBC executor - [x] The **work embedding with** initialization, router, and executor with ShardingSphere - [ ] Use ShardingSphere **parser** instead of the Calcite parser to parse SQL (SqlNodeConverter, @guimingyue) - [ ] Custom **planner** for SQL Optimization(PlannerInitializer, @guimingyue ) - [ ] SQL Optimization for `CalciteFilterableTable` (CalciteExecutionSQLGenerator) - [ ] The implement for `CalciteRawExecutor` (Especially `ResultSetMetadata`) - [ ] The **SQLRouter** of ShardingSphere to route SQL to `CalciteExecutor` ### Unit test - [x] CalciteContextFactory - [ ] CalciteLogicSchemaFactory(Doing, ) - [ ] CalciteJDBCExecutor(Doing, #8883) - [ ] CalciteRawExecutor(TODO) ### SQL Federation - [x] Binding tables (Native) - [x] Single table and Broadcast table (Native) - [x] Sharding table and Broadcast table (Native) - [x] Broadcast table and Broadcast table (Native) - [x] Single table and Single table - [ ] Single table and Sharding table - [ ] Sharding table and Sharding table ### Scenario - [x] Sharding - [ ] PrimaryReplica - [ ] Encryption - [ ] Hybrid ---------------------------------------------------------------- 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]
