Calcite is extremely flexible, you can assemble an optimizer manually, to do exactly what you want. Here is our example: https://github.com/feldera/dbsp/blob/2d8498e8a18c6895718ff7fe9d38efa311bdb05f/sql-to-dbsp-compiler/SQL-compiler/src/main/java/org/dbsp/sqlCompiler/compiler/frontend/calciteCompiler/CalciteCompiler.java#L314
Mihai -----Original Message----- From: brunofsdias Sent: Saturday, July 01, 2023 10:03 AM To: [email protected] Subject: Developing problems with Calcite - Need help Hello. My name is Bruno, and I'm a Software Engineer student at University of Minho. I am developing a Calcite application that works like a translator from SQL to Unicage language. Whenever i do a Join with Selection of Rows, it just always seems to do the pushing of the LogicalProject and the LogicalSort past the Join. I have tried to remove the rules that can transpose the Filter, Sort and Joins, and ddi change the computeSelfOfCost functions so that the Join tries to be done first, but then it just always does a scan of the file. Can you help me with this? What can be the best solution? Com os melhores cumprimentos, Bruno Dias...
