Hello Andrey, The issue with the indexes for such a plain query seems major IMHO. So at version 2.0 adding hints will be supported? Is this final?
However, even with no indexes, the query execution time it too much for in-memory (time=8645 ms). I have streamed to cache a single table of ~1_600_000 rows/objects. Each object has many fields ~50 fields most of them Double (cannot be primitives cause I need to have NULL as well for the business logic executed on them). As for the PARTITIONED approach I am aware of it but it does not fit well to the nature of the calculations I have to run which I described in my previous posts of this thread. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12263.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
