Yes, I have used @QuerySqlField(index = true) in MyClass. And here's my
query plan using explain.
============== Start time ===== 2017-06-02 15:11:45.454
***Query executed === >2017-06-02 15:11:45.455
[SELECT
__Z0.FIELD1 AS __C0_0,
__Z0.VALUE2 AS __C0_1
FROM "Test_CacheConfig".MYCLASS__Z0
/* "Test_CacheConfig".INDEXGRP1: MINIPVAL <= ?1 */
WHERE __Z0.FIELD1<= ?1]
[SELECT
__C0_0 AS MINIPVAL,
__C0_1 AS NETWORK
FROM PUBLIC.__T0
/* "Test_CacheConfig"."merge_scan" */]
Seems like query only takes 1 ms. But the when I fetch results from
cursor.getAll() it is taking 100 ms to 1 sec.
Thank you,
Prathamesh Joshi.
Mob : +91 9960414777 | Skype : [email protected]
------ Original Message ------
From: "alexey.goncharuk [via Apache Ignite Users]"
<[email protected]>
To: "Pratham Joshi" <[email protected]>
Sent: 6/2/2017 2:58:47 PM
Subject: Re: In Ignite 2.0.0 - cusrsor.getAll() takes very long time to
retrieve data.
>How do you configure field1 to be an indexed field? Do you use
>@QuerySqlField annotation? Can you share the execution plan of your
>query (you need to run "explain select ..." query)?
>Also, what is the result set size of your query?
>
>--AG
>
>2017-05-30 14:49 GMT+03:00 Pratham Joshi <[hidden email]
></user/SendEmail.jtp?type=node&node=13335&i=0>>:
>>Hello Guys,
>> I am using Ignite 2.0.0 with Oracle database while. By implementing
>>CacheStore I store put data in the cache. I am having geolocation and
>>IP
>>data almost 35m rows.
>>I use id from DB row as key and corresponding row as the value of
>>CacheConfiguration.
>> Like,
>>* CacheConfiguration<Long, MyClass> cfg = new CacheConfiguration<Long,
>>MyClass>();*
>>
>>When I query data like
>>*SqlFieldsQuery sql = new SqlFieldsQuery("select * from MyTable where
>>field1<= some_value);
>>QueryCursor<List<?>> cursor = cache.query(sql);
>>System.out.println(cursor.getAll().get(0));*
>>
>>Now here *field1 *is an indexed field from MyClass(not the one I have
>>used
>>as key) the cursor.getAll() operation takes very long time to retrieve
>>the
>>result.
>>
>>I suppose that I am certainly missing some configuration, but couldn't
>>figure out what.
>>Thanks in advance
>>
>>
>>
>>
>>
>>--
>>View this message in context:
>>http://apache-ignite-users.70518.x6.nabble.com/In-Ignite-2-0-0-cusrsor-getAll-takes-very-long-time-to-retrieve-data-tp13224.html
>>
>><http://apache-ignite-users.70518.x6.nabble.com/In-Ignite-2-0-0-cusrsor-getAll-takes-very-long-time-to-retrieve-data-tp13224.html>
>>Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
>
>
>--------------------------------------------------------------------------------
>If you reply to this email, your message will be added to the
>discussion below:
>http://apache-ignite-users.70518.x6.nabble.com/In-Ignite-2-0-0-cusrsor-getAll-takes-very-long-time-to-retrieve-data-tp13224p13335.html
> To unsubscribe from In Ignite 2.0.0 -
> cusrsor.getAll() takes very
>long time to retrieve data., click here
><http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=13224&code=cHJhdGhhbWVzaGpAdnJoeXRobXN0ZWNoLmNvbXwxMzIyNHwtMTI4NTQ3NDI5>.
>NAML
><http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/In-Ignite-2-0-0-cusrsor-getAll-takes-very-long-time-to-retrieve-data-tp13224p13336.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
