You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Ilya Kasnacheev <il...@gmail.com> on 2018/07/02 13:53:03 UTC
Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery
Hello!
You can set IGNITE_SQL_LAZY_RESULT_SET=true (environment variable or JVM
system property) on all nodes since Apache Ignite 2.5, make sure that all
queries run with lazy=true.
It will still not save you from some scenarios such as runaway GROUP BYs,
but from SELECT * it would.
Regards,
--
Ilya Kasnacheev
2018-06-28 23:17 GMT+03:00 ApacheUser <bh...@gmail.com>:
> Evgenii,
> what happens if the user doesn't set that limit or forget to set on client
> tool?,
>
> we set that but some one testing without the lazy=true to prove that Apache
> Ignite is not stable.
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by "ilya.kasnacheev" <il...@gmail.com>.
Hello!
I'm not aware of any other settings to avoid OOME for SQL queries.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by ApacheUser <bh...@gmail.com>.
Hello Ilya Kasnacheev,
using Ignite 2.6.
SQL through Tableau using ODBC connection is getting OOME when selct 8 from
table without limit.
I have set export IGNITE_SQL_FORCE_LAZY_RESULT_SET=true in ignite.sh.
What else should I configure to avoid OOME when using ODBC?
thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by ApacheUser <bh...@gmail.com>.
Great,
It works perfectly, thankyou.
Bhaskar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
You have to put export before it to pass it to Apache Ignite:
export IGNITE_SQL_FORCE_LAZY_RESULT_SET=true
Regards,
--
Ilya Kasnacheev
2018-08-01 16:58 GMT+03:00 ApacheUser <bh...@gmail.com>:
> Hello Ilya Kasnacheev,
>
> I set IGNITE_SQL_FORCE_LAZY_RESULT_SET=true just below
> ENABLE_ASSERTIONS="0" in ignite.sh but still I am getting out of memory
> error when I do select * from table. Is this right place to set this
> parameter? please confirm.
>
>
> Thanks
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by ApacheUser <bh...@gmail.com>.
Hello Ilya Kasnacheev,
I set IGNITE_SQL_FORCE_LAZY_RESULT_SET=true just below
ENABLE_ASSERTIONS="0" in ignite.sh but still I am getting out of memory
error when I do select * from table. Is this right place to set this
parameter? please confirm.
Thanks
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I'm not aware of such parameters.
Regards,
--
Ilya Kasnacheev
2018-07-03 19:18 GMT+03:00 ApacheUser <bh...@gmail.com>:
> Thanks Ilya,
> Appreciate your help,
>
> Is there any parameter in COnfig file to control the number of rows or
> amount of resources a clinet connection can use and if exceeds disconnect?
>
> thanks
> Bhaskar
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by ApacheUser <bh...@gmail.com>.
Thanks Ilya,
Appreciate your help,
Is there any parameter in COnfig file to control the number of rows or
amount of resources a clinet connection can use and if exceeds disconnect?
thanks
Bhaskar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
Unfortunately I'm not aware of any practices that will make Ignite (or
indeed any DB) foolproof. I know that people use human DBAs for that
purpose, which control which statements are allowed to be run on production
and which aren't.
Regards,
--
Ilya Kasnacheev
2018-07-02 21:01 GMT+03:00 ApacheUser <bh...@gmail.com>:
> Thanks Ily ,
> could share any guidelines to control groupby?, Like didicated client nodes
> for connectivity from Tableau and SQL?
> Thanks
> Bhaskar
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>
Re: SqlFieldsQuery Cannot create inner bean
'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by ApacheUser <bh...@gmail.com>.
Thanks Ily ,
could share any guidelines to control groupby?, Like didicated client nodes
for connectivity from Tableau and SQL?
Thanks
Bhaskar
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello again!
It seems that I had a copy-paste problem here: the actual flag name is
IGNITE_SQL_FORCE_LAZY_RESULT_SET
Regards,
--
Ilya Kasnacheev
2018-07-02 16:53 GMT+03:00 Ilya Kasnacheev <il...@gmail.com>:
> Hello!
>
> You can set IGNITE_SQL_LAZY_RESULT_SET=true (environment variable or JVM
> system property) on all nodes since Apache Ignite 2.5, make sure that all
> queries run with lazy=true.
>
> It will still not save you from some scenarios such as runaway GROUP BYs,
> but from SELECT * it would.
>
> Regards,
>
> --
> Ilya Kasnacheev
>
> 2018-06-28 23:17 GMT+03:00 ApacheUser <bh...@gmail.com>:
>
>> Evgenii,
>> what happens if the user doesn't set that limit or forget to set on client
>> tool?,
>>
>> we set that but some one testing without the lazy=true to prove that
>> Apache
>> Ignite is not stable.
>>
>> Thanks
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
>
>