回复： Fetched result set too large
I see. Thanks a lot! 2017年09月19日 13:49,slava.koptilin : Hi Lucky, You just need to start grid with -DIGNITE_SQL_MERGE_TABLE_MAX_SIZE=3 JVM flag. Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: 回复： Fetched result set too large
Hi Lucky, You just need to start grid with -DIGNITE_SQL_MERGE_TABLE_MAX_SIZE=3 JVM flag. Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
回复： Fetched result set too large
I see the document you refer to.but I don't know how to set this property
value.
I excepted to use java code .
Is there any example?
Thanks.
Lucky
2017年09月18日 22:50,Вячеслав Коптилин :
Hi Lucky,
It seems that I was wrong.
You need to increase the value of
IgniteSystemProperty#IGNITE_SQL_MERGE_TABLE_MAX_SIZE [1]
The default value is 10 000.
[1]
https://ignite.apache.org/releases/2.1.0/javadoc/org/apache/ignite/IgniteSystemProperties.html#IGNITE_SQL_MERGE_TABLE_MAX_SIZE
Thanks.
2017-09-12 9:50 GMT+03:00 Lucky :
Hi
I use jdbc to fetch result from cache.
Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
Connection conn =DriverManager.getConnection("jdbc:ignite:thin://IP");
ResultSet rs = conn.createStatement().executeQuery(sql);
And the sql is like this:
select v.id,v.name,v.seq from (selet a.id as id,b.name as name,c.seq as seq
from a inner join b on a.id= b.id left outer join c on a.id=c.id) v left outer
join (select did from d where cid in(Ids) group by did having count(did)>=3000)
w on v.id = d.did where d.did is null
when 'select did from d where cid in(Ids) group by did having count(did)>=3000'
return few records ,this sql is work,but if it return 20,000 records(actually
it's often return 10 million records),it got this wrong message:Fetched result
set war too large.
And the whole sql is expected 30,000 records.
Any suggestion? Thanks.
Lucky.
Re: Fetched result set too large
Hi Lucky,
It seems that I was wrong.
You need to increase the value of
IgniteSystemProperty#IGNITE_SQL_MERGE_TABLE_MAX_SIZE [1]
The default value is 10 000.
[1]
https://ignite.apache.org/releases/2.1.0/javadoc/org/apache/ignite/IgniteSystemProperties.html#IGNITE_SQL_MERGE_TABLE_MAX_SIZE
Thanks.
2017-09-12 9:50 GMT+03:00 Lucky :
> Hi
> I use jdbc to fetch result from cache.
> Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
> Connection conn = DriverManager.getConnection("jdbc:ignite:thin://IP");
> ResultSet rs = conn.createStatement().executeQuery(sql);
>
> And the sql is like this:
> select v.id,v.name,v.seq from (selet a.id as id,b.name as name,c.seq as
> seq from a inner join b on a.id= b.id left outer join c on a.id=c.id) v
> left outer join (select did from d where cid in(Ids) group by did having
> count(did)>=3000) w on v.id = d.did where d.did is null
>
> when 'select did from d where cid in(Ids) group by did having
> count(did)>=3000' return few records ,this sql is work,but if it return
> 20,000 records(actually it's often return 10 million records),it got this
> wrong message:Fetched result set war too large.
>
> And the whole sql is expected 30,000 records.
> Any suggestion? Thanks.
> Lucky.
>
>
>
>
Re:Re: Re: Re: Fetched result set too large
Yes,It work. Thank you. At 2017-09-14 00:26:07, "Alexey Kuznetsov" wrote: Hi Lucky, You can build Ignite from sources. Will this work for you? On Wed, Sep 13, 2017 at 9:07 PM, Lucky wrote: Oh,No! This is the worst news today. I have to try another way to resolve it. Anyway,Thanks a lot. At 2017-09-13 14:46:00, "Вячеслав Коптилин" wrote: Hi Lucky, Unfortunately, there is no release date on Apache Ignite releases page [1]. Usually, new Ignite release become available twice a year. [1] https://issues.apache.org/jira/projects/IGNITE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page Thanks. 2017-09-13 5:27 GMT+03:00 Lucky : Thanks. When will the 2.3 be released? At 2017-09-12 22:58:34, "slava.koptilin" wrote: >Hi Lucky, > >It seems that this issue was resolved >https://issues.apache.org/jira/browse/IGNITE-5991 >The fix will be available in Apache Ignite 2.3 > >Thanks! > > > > >-- >Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Alexey Kuznetsov
Re: Re: Re: Fetched result set too large
Hi Lucky, You can build Ignite from sources. Will this work for you? On Wed, Sep 13, 2017 at 9:07 PM, Lucky wrote: > Oh,No! > This is the worst news today. > I have to try another way to resolve it. > > Anyway,Thanks a lot. > > > > > At 2017-09-13 14:46:00, "Вячеслав Коптилин" > wrote: > > Hi Lucky, > > Unfortunately, there is no release date on Apache Ignite releases page [1]. > Usually, new Ignite release become available twice a year. > > [1] https://issues.apache.org/jira/projects/IGNITE? > selectedItem=com.atlassian.jira.jira-projects-plugin:release-page > > Thanks. > > 2017-09-13 5:27 GMT+03:00 Lucky : > >> Thanks. >> When will the 2.3 be released? >> >> >> >> At 2017-09-12 22:58:34, "slava.koptilin" wrote: >> >Hi Lucky, >> > >> >It seems that this issue was resolved >> >https://issues.apache.org/jira/browse/IGNITE-5991 >> >The fix will be available in Apache Ignite 2.3 >> > >> >Thanks! >> > >> > >> > >> > >> >-- >> >Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> >> >> >> >> > > > > > -- Alexey Kuznetsov
Re:Re: Re: Fetched result set too large
Oh,No! This is the worst news today. I have to try another way to resolve it. Anyway,Thanks a lot. At 2017-09-13 14:46:00, "Вячеслав Коптилин" wrote: Hi Lucky, Unfortunately, there is no release date on Apache Ignite releases page [1]. Usually, new Ignite release become available twice a year. [1] https://issues.apache.org/jira/projects/IGNITE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page Thanks. 2017-09-13 5:27 GMT+03:00 Lucky : Thanks. When will the 2.3 be released? At 2017-09-12 22:58:34, "slava.koptilin" wrote: >Hi Lucky, > >It seems that this issue was resolved >https://issues.apache.org/jira/browse/IGNITE-5991 >The fix will be available in Apache Ignite 2.3 > >Thanks! > > > > >-- >Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Re: Fetched result set too large
Hi Lucky, Unfortunately, there is no release date on Apache Ignite releases page [1]. Usually, new Ignite release become available twice a year. [1] https://issues.apache.org/jira/projects/IGNITE?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page Thanks. 2017-09-13 5:27 GMT+03:00 Lucky : > Thanks. > When will the 2.3 be released? > > > > At 2017-09-12 22:58:34, "slava.koptilin" wrote: > >Hi Lucky, > > > >It seems that this issue was resolved > >https://issues.apache.org/jira/browse/IGNITE-5991 > >The fix will be available in Apache Ignite 2.3 > > > >Thanks! > > > > > > > > > >-- > >Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > > > >
Re:Re: Fetched result set too large
Thanks. When will the 2.3 be released? At 2017-09-12 22:58:34, "slava.koptilin" wrote: >Hi Lucky, > >It seems that this issue was resolved >https://issues.apache.org/jira/browse/IGNITE-5991 >The fix will be available in Apache Ignite 2.3 > >Thanks! > > > > >-- >Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Fetched result set too large
Hi Lucky, It seems that this issue was resolved https://issues.apache.org/jira/browse/IGNITE-5991 The fix will be available in Apache Ignite 2.3 Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Fetched result set too large
Hi
I use jdbc to fetch result from cache.
Class.forName("org.apache.ignite.IgniteJdbcThinDriver");
Connection conn =DriverManager.getConnection("jdbc:ignite:thin://IP");
ResultSet rs = conn.createStatement().executeQuery(sql);
And the sql is like this:
select v.id,v.name,v.seq from (selet a.id as id,b.name as name,c.seq as seq
from a inner join b on a.id= b.id left outer join c on a.id=c.id) v left outer
join (select did from d where cid in(Ids) group by did having count(did)>=3000)
w on v.id = d.did where d.did is null
when 'select did from d where cid in(Ids) group by did having count(did)>=3000'
return few records ,this sql is work,but if it return 20,000 records(actually
it's often return 10 million records),it got this wrong message:Fetched result
set war too large.
And the whole sql is expected 30,000 records.
Any suggestion? Thanks.
Lucky.
