ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@gridgain.com>
Subject Re: Sql query performance with partitioned caches
Date Wed, 27 Jan 2016 11:59:52 GMT
Hi Andrey,

In terms of Ignite or any other in-memory product there is no reason to 
use an SQL query there cause when you need to get an object(s) by key(s) 
you should use cache.get(key)/cache.getKeys(key) that sends request(s) 
only to primary node(s).
That's it and I wouldn't make SQL engine more complex just in order to 
detect such queries that can be optimized because a developer can take 
care of this.


On 1/27/2016 10:15 AM, Andrey Nestrogaev wrote:
> Hi Valentin,
> 1. We have partitioned cache "myCache" where store entities like Account(id,
> name)
> 2. key = id e.g. cache.put(1, new Account(1,"account 1"));
> 3. Assume I execute throuth jdbc query "select * from account where id=1", i
> want that query doesn't broadcast on every node.
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Sql-query-performance-with-partitioned-caches-tp2700p2734.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message