Hi, ignite guys I thought that Apache Ignite does what apache drill does[1], but it makes me surprised that Ignite uses a top-down calcite optimizer [2]. But I believe some issues blocks top-down [3].
Except for apace drill, both hazelcast[4] and Flink[5] split optimization into two independent phases - logical and physical. Why did Ignite make such a technical decision? Thanks - Chang [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-37%3A+New+query+execution+engine [2] https://issues.apache.org/jira/browse/IGNITE-13117 [3] https://issues.apache.org/jira/browse/CALCITE-4052 [4] https://github.com/hazelcast/hazelcast [5] https://github.com/apache/flink
