Responded in [1]. Let's continue the discussion there.
[1]
http://apache-ignite-users.70518.x6.nabble.com/multiple-value-key-td4138.html
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/querying-sql-performance-of-apache-ignite-tp4135p4204.html
Sent from th
I think that I unclearly showed my case:
1. I have timestamp, something of form: 2001-01-21-21:31:12.121. Now I am
going to set it as key. Tell me,
Will it be possible to load cache all rows with timestamp from 2000 year to
2001 ?
We know, that given the fact that key is timestamp then
get('2001-0
1. Yes, this is possible.
2. In a key-value storage, each entry has to have unique key. Entries with
the equal keys will overwrite each other.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/querying-sql-performance-of-apache-ignite-tp4135p4188.html
Sent fr
Try to reply to my:
1. When my key is timestamp. Ii it possible to load to cache memory all rows
from year 2000 to year 2012 ?
2. When my key is timestamp and id (Integer). Is it possible to load load to
cache memory all rows from year 2000 to year 2012 ? Note, that I don't set
value of key id (onl
Read-through works for key-based access (methods like get, remove, invoke,
etc.), but not for SQL queries. That's because Ignite doesn't know what data
it will need for the query prior to running it. But you can preload it
manually.
-Val
--
View this message in context:
http://apache-ignite-us
in.kuliche...@gmail.com]
发送时间: 2016年4月14日 5:24
收件人: user@ignite.apache.org
主题: Re: querying, sql performance of apache ignite
Hi,
1. This is correct, current implementation of SQL queries only data that is
already in memory. This is enough for majority of use cases, because usually
in-memory sy
Hi,
1. This is correct, current implementation of SQL queries only data that is
already in memory. This is enough for majority of use cases, because usually
in-memory systems deal with operational data sets (i.e. subsets of "hot",
most frequently accessed data) and can safely ignore the rest of th
