Re: Re[2]: Apache Ignite H2 Vulnerabilities

[Lokesh Bandaru]

Hello Stephen, the document(ReadMe) you shared earlier, has mentioned that
ignite-calcite must be declared as a dependency.
In this case, it would be, org.apache.ignite:ignite-calcite:2.13.0 right!.
But, which, at the moment, is not available.
Can you please advise?

On Thu, Apr 28, 2022 at 5:21 PM Zhenya Stanilovsky 
wrote:

> Seems it would be published with new documentation, Nikita Amelchev isn`t
> it ? check [1]
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15189
>
>
> Thank you Stephen.
> Is there also a writeup summarizing what is/isn't supported with this
> 'experimental' feature?
>
> On Thu, Apr 28, 2022 at 4:30 PM Stephen Darlington <
> stephen.darling...@gridgain.com
> >
> wrote:
>
> https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt
>
>
> On 28 Apr 2022, at 11:46, Lokesh Bandaru  > wrote:
>
> Thanks Ilya.
>
> Version 2.13 has come out but still seems to be shipping with the same
> vulnerability-ridden version of h2 database.
> The documentation doesn't mention if/how Calcite is turned on.
> Can you advise on how it can be enabled?
>
> On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol  > wrote:
>
> Hi Lokesh,
>
> Updates for running Ignite over Java 17 is already in master. Please
> take a look:
> https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh
>
> On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
>  > You are fast. :) Was just typing a reply on top of the last one and
> yours
>  > is already here.
>  >
>  > Ignore the last question, found this,
>  > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 .
>  > *Looking forward to this release. *
>  >
>  > *One slightly unrelated question, feel free to ignore. *
>  > *I know there is no support(or certified) for any version of Java
> greater
>  > than 11. *
>  > *What would it take for 2.13 to be able to run on Java17?*
>  >
>  > On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
>  > stephen.darling...@gridgain.com
> >
> wrote:
>  >
>  > > Code freeze was yesterday. The target release date is 22 April.
>  > >
>  > > More here: Apache+Ignite+2.13
>  > > <
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13>
>  > >
>  > > On 12 Apr 2022, at 11:03, Lokesh Bandaru  > wrote:
>  > >
>  > > Thanks for getting back, Stephen.
>  > > I am aware that Calcite is in the plans.
>  > > Any tentative timeline as to when 2.13(beta/ga) is going to be made
>  > > available?
>  > >
>  > > Regards.
>  > >
>  > > On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
>  > > stephen.darling...@gridgain.com
> >
> wrote:
>  > >
>  > >> The H2 project removed support for Ignite some time ago (
>  > >> https://github.com/h2database/h2database/pull/2227) which makes it
>  > >> difficult to move to newer versions.
>  > >>
>  > >> The next version of Ignite (2.13) has an alternative SQL engine
> (Apache
>  > >> Calcite) so over time there will be no need for H2.
>  > >>
>  > >> On 11 Apr 2022, at 20:34, Lokesh Bandaru  > wrote:
>  > >>
>  > >> Resending.
>  > >>
>  > >> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru  >
>  > >> wrote:
>  > >>
>  > >>> Hello there, hi
>  > >>>
>  > >>> Writing to you with regards to the security
> vulnerabilities(particularly
>  > >>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2
> database and
>  > >>> the Apache Ignite's dependency on the flagged versions of H2.
>  > >>> There is an open issue tracking this,
>  > >>> https://issues.apache.org/jira/browse/IGNITE-16542, which doesn't
> seem
>  > >>> to have been fully addressed yet.
>  > >>> Have these problems been overcome already? Can you please advise?
>  > >>>
>  > >>> Thanks.
>  > >>>
>  > >>
>  > >>
>  > >
>  >
>
>
>
>
>
>

Re: Unable to remove cache key entries after Ignite server restart

[Sumit Deshinge]

Note that this is not happening with all the data set but only for cache
entries which were written into ignite before server restart and tried to
be deleted after restart.

On Thu, Apr 28, 2022 at 10:18 PM Sumit Deshinge 
wrote:

> Hi,
>
> I am using ignite with native persistence enabled along with cache write
> sync mode as FULL_SYNC and cache rebalance mode as sync.
>
> In normal workflow where there is no restart, I can see all data is being
> written, read and deleted from cache successfully.
>
> But in case of ignite server restart, where some of the data is written
> before restart, for the same set of data after restart, ignite is able to
> read that data but not able to remove it from the cache.
> I verified the hashcode and equals for the key I am using for remove and
> the one in ignite is same.
> But still remove operation does not actually remove data from cache.
> Checked what's the result of contains operation and it gives false.
>
> This is observed only in case of restart. I can see there are warning as
> below after restart but I expect ignite just gives these warnings before it
> recovers :
> - Ignite node stopped in the middle of checkpoint. Will restore memory
> state and finish checkpoint on node start.
> - Started cache in recovery mode 
> - Finished recovery for cache 
>
> Any idea or configuration that needs to be done during such case ?
>
> --
> Regards,
> Sumit Deshinge
>
>

-- 
Regards,
Sumit Deshinge

Unable to remove cache key entries after Ignite server restart

[Sumit Deshinge]

Hi,

I am using ignite with native persistence enabled along with cache write
sync mode as FULL_SYNC and cache rebalance mode as sync.

In normal workflow where there is no restart, I can see all data is being
written, read and deleted from cache successfully.

But in case of ignite server restart, where some of the data is written
before restart, for the same set of data after restart, ignite is able to
read that data but not able to remove it from the cache.
I verified the hashcode and equals for the key I am using for remove and
the one in ignite is same.
But still remove operation does not actually remove data from cache.
Checked what's the result of contains operation and it gives false.

This is observed only in case of restart. I can see there are warning as
below after restart but I expect ignite just gives these warnings before it
recovers :
- Ignite node stopped in the middle of checkpoint. Will restore memory
state and finish checkpoint on node start.
- Started cache in recovery mode 
- Finished recovery for cache 

Any idea or configuration that needs to be done during such case ?

-- 
Regards,
Sumit Deshinge

[ANNOUNCE] Apache Ignite 2.13.0 Released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.13.0.

Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org

The Apache Ignite community has made a lot of changes in the 2.13.0
release. This blog post will help you to know about some valuable
improvements:
https://blogs.apache.org/ignite/entry/apache-ignite-2-13-0

For the full list of changes, you can refer to the RELEASE_NOTES list
which is trying to catalogue the most significant improvements for
this version of the database:
https://ignite.apache.org/releases/2.13.0/release_notes.html

Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi

Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask


Regards,
Nikita Amelchev on behalf of the Apache Ignite community.

Re[2]: Apache Ignite H2 Vulnerabilities

[Zhenya Stanilovsky]

Seems it would be published with new documentation, Nikita Amelchev isn`t it ? 
check [1]
 
[1]  https://issues.apache.org/jira/browse/IGNITE-15189
 
>Thank you Stephen. 
>Is there also a writeup summarizing what is/isn't supported with this 
>'experimental' feature?  
>On Thu, Apr 28, 2022 at 4:30 PM Stephen Darlington < 
>stephen.darling...@gridgain.com > wrote:
>>https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt
>> 
>>>On 28 Apr 2022, at 11:46, Lokesh Bandaru < lokeshband...@gmail.com > wrote:  
>>>Thanks Ilya. 
>>> 
>>>Version 2.13 has come out but still seems to be shipping with the same 
>>>vulnerability-ridden version of h2 database. 
>>>The documentation doesn't mention if/how Calcite is turned on. 
>>>Can you advise on how it can be enabled?   
>>>On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol < llivezk...@gmail.com > wrote:
Hi Lokesh,

Updates for running Ignite over Java 17 is already in master. Please
take a look:
https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh

On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
 > You are fast. :) Was just typing a reply on top of the last one and yours
 > is already here.
 >
 > Ignore the last question, found this,
 >  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 .
 > *Looking forward to this release. *
 >
 > *One slightly unrelated question, feel free to ignore. *
 > *I know there is no support(or certified) for any version of Java greater
 > than 11. *
 > *What would it take for 2.13 to be able to run on Java17?*
 >
 > On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
 >  stephen.darling...@gridgain.com > wrote:
 >
 > > Code freeze was yesterday. The target release date is 22 April.
 > >
 > > More here: Apache+Ignite+2.13
 > > < 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 >
 > >
 > > On 12 Apr 2022, at 11:03, Lokesh Bandaru < lo...@gmail.com > wrote:
 > >
 > > Thanks for getting back, Stephen.
 > > I am aware that Calcite is in the plans.
 > > Any tentative timeline as to when 2.13(beta/ga) is going to be made
 > > available?
 > >
 > > Regards.
 > >
 > > On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
 > >  stephen.darling...@gridgain.com > wrote:
 > >
 > >> The H2 project removed support for Ignite some time ago (
 > >>  https://github.com/h2database/h2database/pull/2227 ) which makes it
 > >> difficult to move to newer versions.
 > >>
 > >> The next version of Ignite (2.13) has an alternative SQL engine
(Apache
 > >> Calcite) so over time there will be no need for H2.
 > >>
 > >> On 11 Apr 2022, at 20:34, Lokesh Bandaru < lo...@gmail.com > wrote:
 > >>
 > >> Resending.
 > >>
 > >> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru < lo...@gmail.com >
 > >> wrote:
 > >>
 > >>> Hello there, hi
 > >>>
 > >>> Writing to you with regards to the security
vulnerabilities(particularly
 > >>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2
database and
 > >>> the Apache Ignite's dependency on the flagged versions of H2.
 > >>> There is an open issue tracking this,
 > >>>  https://issues.apache.org/jira/browse/IGNITE-16542 , which doesn't
seem
 > >>> to have been fully addressed yet.
 > >>> Have these problems been overcome already? Can you please advise?
 > >>>
 > >>> Thanks.
 > >>>
 > >>
 > >>
 > >
 > 
 
 
 
 

Is apache ignite suitable for sql querying on ignite cache?

[Reshma Bochare]

Hi Team,
We want to use apache ignite for below use case.
We provide reports to customer . We execute query on oracle and feed it into 
oracle. And on the top of report, we allow pagination, sorting, grouping and 
export etc. Right now for each and every action after report execution, we hit 
oracle to get data. So we want we will hit oracle once and get data in memory 
and execute query on memory data to get data of further operations like 
pagination, sorting, grouping and export .
To achieve this, I am thinking to use of apache ignite as below


1.   We execute query on oracle database and want to save that data into 
apache ignite as cache. (Like memory store, persistence mode enabled)

2.   And on ignite cache, execute some complicated queries and fetch data 
from ignite cache.

3.   Keep the expiry of this cache to 5 minutes.

4.   So there will be lot of insertion of new data and at the same time get 
of cache also like User executes report and performs some grouping, and closes 
report. In this case we will create cache in ignite and keep in the memory till 
user closes it. Meanwhile perform sql queries on ignite cache.

5.   For cache, considering creating class with different data types fields 
to it. And perform query on this class

Is it apache ignite suitable for this use case.?

Thanks,
Reshma.





This message, together with any attachments, is intended only for the use of 
the individual or entity to which it is addressed and may contain confidential 
and/or privileged information. If you are not the intended recipient(s), or the 
employee or agent responsible for delivery of this message to the intended 
recipient(s), you are hereby notified that any dissemination, distribution or 
copying of this message, or any attachment, is strictly prohibited. If you have 
received this message in error, please immediately notify the sender and delete 
the message, together with any attachments, from your computer. Thank you for 
your cooperation.

Re: Apache Ignite H2 Vulnerabilities

[Lokesh Bandaru]

Thank you Stephen.
Is there also a writeup summarizing what is/isn't supported with this
'experimental' feature?

On Thu, Apr 28, 2022 at 4:30 PM Stephen Darlington <
stephen.darling...@gridgain.com> wrote:

> https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt
>
> On 28 Apr 2022, at 11:46, Lokesh Bandaru  wrote:
>
> Thanks Ilya.
>
> Version 2.13 has come out but still seems to be shipping with the same
> vulnerability-ridden version of h2 database.
> The documentation doesn't mention if/how Calcite is turned on.
> Can you advise on how it can be enabled?
>
> On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol  wrote:
>
>> Hi Lokesh,
>>
>> Updates for running Ignite over Java 17 is already in master. Please
>> take a look:
>> https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh
>>
>> On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
>>  > You are fast. :) Was just typing a reply on top of the last one and
>> yours
>>  > is already here.
>>  >
>>  > Ignore the last question, found this,
>>  > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
>> .
>>  > *Looking forward to this release. *
>>  >
>>  > *One slightly unrelated question, feel free to ignore. *
>>  > *I know there is no support(or certified) for any version of Java
>> greater
>>  > than 11. *
>>  > *What would it take for 2.13 to be able to run on Java17?*
>>  >
>>  > On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
>>  > stephen.darling...@gridgain.com> wrote:
>>  >
>>  > > Code freeze was yesterday. The target release date is 22 April.
>>  > >
>>  > > More here: Apache+Ignite+2.13
>>  > > <
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13>
>>  > >
>>  > > On 12 Apr 2022, at 11:03, Lokesh Bandaru  wrote:
>>  > >
>>  > > Thanks for getting back, Stephen.
>>  > > I am aware that Calcite is in the plans.
>>  > > Any tentative timeline as to when 2.13(beta/ga) is going to be made
>>  > > available?
>>  > >
>>  > > Regards.
>>  > >
>>  > > On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
>>  > > stephen.darling...@gridgain.com> wrote:
>>  > >
>>  > >> The H2 project removed support for Ignite some time ago (
>>  > >> https://github.com/h2database/h2database/pull/2227) which makes it
>>  > >> difficult to move to newer versions.
>>  > >>
>>  > >> The next version of Ignite (2.13) has an alternative SQL engine
>> (Apache
>>  > >> Calcite) so over time there will be no need for H2.
>>  > >>
>>  > >> On 11 Apr 2022, at 20:34, Lokesh Bandaru  wrote:
>>  > >>
>>  > >> Resending.
>>  > >>
>>  > >> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru 
>>  > >> wrote:
>>  > >>
>>  > >>> Hello there, hi
>>  > >>>
>>  > >>> Writing to you with regards to the security
>> vulnerabilities(particularly
>>  > >>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2
>> database and
>>  > >>> the Apache Ignite's dependency on the flagged versions of H2.
>>  > >>> There is an open issue tracking this,
>>  > >>> https://issues.apache.org/jira/browse/IGNITE-16542, which doesn't
>> seem
>>  > >>> to have been fully addressed yet.
>>  > >>> Have these problems been overcome already? Can you please advise?
>>  > >>>
>>  > >>> Thanks.
>>  > >>>
>>  > >>
>>  > >>
>>  > >
>>  >
>>
>
>

Re: Apache Ignite H2 Vulnerabilities

[Stephen Darlington]

https://github.com/apache/ignite/blob/2.13.0/modules/calcite/README.txt

> On 28 Apr 2022, at 11:46, Lokesh Bandaru  wrote:
> 
> Thanks Ilya. 
> 
> Version 2.13 has come out but still seems to be shipping with the same 
> vulnerability-ridden version of h2 database. 
> The documentation doesn't mention if/how Calcite is turned on. 
> Can you advise on how it can be enabled? 
> 
> On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol  > wrote:
> Hi Lokesh,
> 
> Updates for running Ignite over Java 17 is already in master. Please 
> take a look: 
> https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh 
> 
> 
> On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
>  > You are fast. :) Was just typing a reply on top of the last one and yours
>  > is already here.
>  >
>  > Ignore the last question, found this,
>  > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 
>  .
>  > *Looking forward to this release. *
>  >
>  > *One slightly unrelated question, feel free to ignore. *
>  > *I know there is no support(or certified) for any version of Java greater
>  > than 11. *
>  > *What would it take for 2.13 to be able to run on Java17?*
>  >
>  > On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
>  > stephen.darling...@gridgain.com > 
> wrote:
>  >
>  > > Code freeze was yesterday. The target release date is 22 April.
>  > >
>  > > More here: Apache+Ignite+2.13
>  > >  >
>  > >
>  > > On 12 Apr 2022, at 11:03, Lokesh Bandaru  > wrote:
>  > >
>  > > Thanks for getting back, Stephen.
>  > > I am aware that Calcite is in the plans.
>  > > Any tentative timeline as to when 2.13(beta/ga) is going to be made
>  > > available?
>  > >
>  > > Regards.
>  > >
>  > > On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
>  > > stephen.darling...@gridgain.com 
> > wrote:
>  > >
>  > >> The H2 project removed support for Ignite some time ago (
>  > >> https://github.com/h2database/h2database/pull/2227 
> ) which makes it
>  > >> difficult to move to newer versions.
>  > >>
>  > >> The next version of Ignite (2.13) has an alternative SQL engine 
> (Apache
>  > >> Calcite) so over time there will be no need for H2.
>  > >>
>  > >> On 11 Apr 2022, at 20:34, Lokesh Bandaru  > wrote:
>  > >>
>  > >> Resending.
>  > >>
>  > >> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru  >
>  > >> wrote:
>  > >>
>  > >>> Hello there, hi
>  > >>>
>  > >>> Writing to you with regards to the security 
> vulnerabilities(particularly
>  > >>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2 
> database and
>  > >>> the Apache Ignite's dependency on the flagged versions of H2.
>  > >>> There is an open issue tracking this,
>  > >>> https://issues.apache.org/jira/browse/IGNITE-16542 
> , which doesn't 
> seem
>  > >>> to have been fully addressed yet.
>  > >>> Have these problems been overcome already? Can you please advise?
>  > >>>
>  > >>> Thanks.
>  > >>>
>  > >>
>  > >>
>  > >
>  >

Re: Re: Apache Ignite H2 Vulnerabilities

[Lokesh Bandaru]

Thanks Ilya.

Version 2.13 has come out but still seems to be shipping with the same
vulnerability-ridden version of h2 database.
The documentation doesn't mention if/how Calcite is turned on.
Can you advise on how it can be enabled?

On Wed, Apr 13, 2022 at 7:29 AM Ilya Korol  wrote:

> Hi Lokesh,
>
> Updates for running Ignite over Java 17 is already in master. Please
> take a look:
> https://github.com/apache/ignite/blob/master/bin/include/jvmdefaults.sh
>
> On 2022/04/12 10:11:57 Lokesh Bandaru wrote:
>  > You are fast. :) Was just typing a reply on top of the last one and
> yours
>  > is already here.
>  >
>  > Ignore the last question, found this,
>  > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13 .
>  > *Looking forward to this release. *
>  >
>  > *One slightly unrelated question, feel free to ignore. *
>  > *I know there is no support(or certified) for any version of Java
> greater
>  > than 11. *
>  > *What would it take for 2.13 to be able to run on Java17?*
>  >
>  > On Tue, Apr 12, 2022 at 3:36 PM Stephen Darlington <
>  > stephen.darling...@gridgain.com> wrote:
>  >
>  > > Code freeze was yesterday. The target release date is 22 April.
>  > >
>  > > More here: Apache+Ignite+2.13
>  > > <
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13>
>  > >
>  > > On 12 Apr 2022, at 11:03, Lokesh Bandaru  wrote:
>  > >
>  > > Thanks for getting back, Stephen.
>  > > I am aware that Calcite is in the plans.
>  > > Any tentative timeline as to when 2.13(beta/ga) is going to be made
>  > > available?
>  > >
>  > > Regards.
>  > >
>  > > On Tue, Apr 12, 2022 at 2:15 PM Stephen Darlington <
>  > > stephen.darling...@gridgain.com> wrote:
>  > >
>  > >> The H2 project removed support for Ignite some time ago (
>  > >> https://github.com/h2database/h2database/pull/2227) which makes it
>  > >> difficult to move to newer versions.
>  > >>
>  > >> The next version of Ignite (2.13) has an alternative SQL engine
> (Apache
>  > >> Calcite) so over time there will be no need for H2.
>  > >>
>  > >> On 11 Apr 2022, at 20:34, Lokesh Bandaru  wrote:
>  > >>
>  > >> Resending.
>  > >>
>  > >> On Mon, Apr 11, 2022 at 6:42 PM Lokesh Bandaru 
>  > >> wrote:
>  > >>
>  > >>> Hello there, hi
>  > >>>
>  > >>> Writing to you with regards to the security
> vulnerabilities(particularly
>  > >>> the most recent ones, CVE-2022-xxx and CVE-2021-xxx) in the H2
> database and
>  > >>> the Apache Ignite's dependency on the flagged versions of H2.
>  > >>> There is an open issue tracking this,
>  > >>> https://issues.apache.org/jira/browse/IGNITE-16542, which doesn't
> seem
>  > >>> to have been fully addressed yet.
>  > >>> Have these problems been overcome already? Can you please advise?
>  > >>>
>  > >>> Thanks.
>  > >>>
>  > >>
>  > >>
>  > >
>  >
>

Re[2]: Query performance

[Zhenya Stanilovsky]

Got it, can you show both sql requests (with strict and non strict criteria) 
and EXPLAIN output in both cases ?
Do you have indexes?
 
>Hey, it's enabled already. Please check the console log in my email   
>On Thu, 28 Apr 2022, 13:16 Zhenya Stanilovsky, < arzamas...@mail.ru > wrote:
>>
>>Hi, can you check the same with lazy [1] flag ? 
>>
>>[1]  
>>https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#setLazy-boolean-
>>   
>>>Hi,
>>>We are running a sql field query to fetch 4million records from ignite 
>>>cache. We have created a group index for all fields used in where clause and 
>>>can see group index used. But the query takes 20 minutes to fetch all 
>>>records. If we provide more strict criteria to fetch only say 500 records, 
>>>it completes in less than 200 millis. This makes me wonder if I am missing 
>>>some configuration to make result fetching faster or I am not using ignite 
>>>correctly for this use case. Below log is printed during query execution.  
>>>Could you please advise me?
>>>
>>>[11:46:30,694][WARNING][query-#8568][GridMapQueryExecutor] Query produced 
>>>big result set.  [fetched=10, duration=120331ms, type=MAP, 
>>>distributedJoin=false, enforceJoinOrder=false, lazy=true, 
>> 
>> 
>> 
>>  
 
 
 
 

Re: Query performance

[Surinder Mehra]

Hey, it's enabled already. Please check the console log in my email

On Thu, 28 Apr 2022, 13:16 Zhenya Stanilovsky,  wrote:

>
> Hi, can you check the same with lazy [1] flag ?
>
> [1]
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#setLazy-boolean-
>
>
> Hi,
> We are running a sql field query to fetch 4million records from ignite
> cache. We have created a group index for all fields used in where clause
> and can see group index used. But the query takes 20 minutes to fetch all
> records. If we provide more strict criteria to fetch only say 500 records,
> it completes in less than 200 millis. This makes me wonder if I am missing
> some configuration to make result fetching faster or I am not using ignite
> correctly for this use case. Below log is printed during query execution.
> Could you please advise me?
>
> [11:46:30,694][WARNING][query-#8568][GridMapQueryExecutor] Query produced
> big result set.  [fetched=10, duration=120331ms, type=MAP,
> distributedJoin=false, enforceJoinOrder=false, lazy=true,
>
>
>
>
>
>

Re: Query performance

[Zhenya Stanilovsky]

Hi, can you check the same with lazy [1] flag ? 

[1]  
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/query/SqlFieldsQuery.html#setLazy-boolean-
 
>Hi,
>We are running a sql field query to fetch 4million records from ignite cache. 
>We have created a group index for all fields used in where clause and can see 
>group index used. But the query takes 20 minutes to fetch all records. If we 
>provide more strict criteria to fetch only say 500 records, it completes in 
>less than 200 millis. This makes me wonder if I am missing some configuration 
>to make result fetching faster or I am not using ignite correctly for this use 
>case. Below log is printed during query execution.  Could you please advise me?
>
>[11:46:30,694][WARNING][query-#8568][GridMapQueryExecutor] Query produced big 
>result set.  [fetched=10, duration=120331ms, type=MAP, 
>distributedJoin=false, enforceJoinOrder=false, lazy=true, 
 
 
 
 

Query performance

[Surinder Mehra]

Hi,
We are running a sql field query to fetch 4million records from ignite
cache. We have created a group index for all fields used in where clause
and can see group index used. But the query takes 20 minutes to fetch all
records. If we provide more strict criteria to fetch only say 500 records,
it completes in less than 200 millis. This makes me wonder if I am missing
some configuration to make result fetching faster or I am not using ignite
correctly for this use case. Below log is printed during query execution.
Could you please advise me?

[11:46:30,694][WARNING][query-#8568][GridMapQueryExecutor] Query produced
big result set.  [fetched=10, duration=120331ms, type=MAP,
distributedJoin=false, enforceJoinOrder=false, lazy=true,