It can't work on the query level, because internally, it divides all indexes into N trees instead of one(where N equals queryParallelism). You can't redefine it after it was created since it will lead to the complete rebuild of all indexes.
Evgenii 2018-06-06 20:55 GMT+03:00 Sanjeev <[email protected]>: > So it looks like that Query parallelism works at Cache level, but it would > make more sense to do it at the Query level, more like a hint in a SQL > query > to control how much parallelism is needed. This way it will be very dynamic > and users would have full control. Default could be 1, but OLAP queries > could define it dynamically on the fly on a per query basis. > > Also, is CacheConfiguration.queryParallelism() call the only way to define > it. Is there no way to define this, after the fact that cache has been > created and loaded. There should be a way to turn this on-off, for now at > Cache level (though would prefer at Query level), through SQL DDL or DML > statements. > > Is this possible now in some way, or do we have to bring the cluster down > and reload all the data? > > Thanks... > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
