Hello,thanks for response.
I see 79 logs like this in about 40w ignite's logs.Such queries are
targeting on different tables and some of them has where conditions.These
logs warn these queries are taking long time.My application only has sqls
like 'select * from XXX'.I also try to execute above sql in a test code with
jdbc thin connection,but get following exception:
Exception in thread "main" java.sql.SQLException: class
org.apache.ignite.binary.BinaryObjectException: Custom objects are not
supported
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:751)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:210)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:473)
at spark.IgniteSql.main(IgniteSql.java:29)
Does ignite's cache mechanism run such queries？BTW,I did not enable on heap
cache.
ezhuravlev wrote
> Hi,
>
> Ignite doesn't run a query like this internally. It's executed in
> client-connector pool, which means that one of your JDBC or ODBC drivers
> send this query. How often do you see something like that?
>
> Evgenii
>
> чт, 22 нояб. 2018 г. в 15:13, yangjiajun <
> 1371549332@
>>:
>
>> Hello.
>>
>> I found a strange sql in ignite logs.I didn't find such sql in my
>> application. The table contains about 7 million data and such table-scan
>> queries can occupy a lot of heap memory. Is this an internal operation?
>> Or
>> is there something wrong in my application?
>>
>> [16:58:53,139][WARNING][client-connector-#218][IgniteH2Indexing] Query
>> execution is too long [time=1188084 ms, sql='SELECT
>> __Z0._KEY __C0_0,
>> __Z0._VAL __C0_1
>> FROM PUBLIC.TABLE_6950_R_1_1 __Z0', plan=
>> SELECT
>> __Z0._KEY AS __C0_0,
>> __Z0._VAL AS __C0_1
>> FROM PUBLIC.TABLE_6950_R_1_1 __Z0
>> /* PUBLIC.TABLE_6950_R_1_1.__SCAN_ */
>> , parameters=[]]
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>>
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
