Hi, H2 uses a cost-based query optimisation strategy for the query-planner. But in the case of Ignite, I suspect that this cannot be leveraged because the client node does not have access to data statistics (distribution, size, etc) throughout the various client nodes...
So how is the query plan devised? Thanks, Jose -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
