--
>
> result size:1
>
> ---
>
> Time used in index cache query: 16ms
>
> Time:16; result2:[50116926]
>
>
>
>
>
> Best regards,
>
> Kevin
>
>
>
> *发件人:* Alexei Scherbakov [mailto:alexey.sc
mailto:alexey.scherbak...@gmail.com]
发送时间: 2016年7月7日 0:59
收件人: user
主题: Re: 答复: ignite group indexing not work problem
Hi, Kevin.
Have you defined other composite indexes including objid, fieldnum fields ?
If yes, try to disable them and check if query picks up correct index.
2016-07-05 15:45 GM
query is :
>
> String qryStr = " explain select guid from IgniteMetaIndex where objid=?
> and fieldnum=? and stringvalue=? ";
>
> …
>
> fieldQry.setArgs( "a1162", 7 ,"18835473249");
>
>
>
> hope you can help me.
>
>
>
>
>
> Best
s( "a1162", 7 ,"18835473249");
hope you can help me.
Best regards,
Kevin
发件人: Alexei Scherbakov [mailto:alexey.scherbak...@gmail.com]
发送时间: 2016年6月29日 0:30
收件人: user
主题: Re: ignite group indexing not work problem
Hi,
I've tried the provided sample and found what inste
[mailto:alexey.scherbak...@gmail.com]
发送时间: 2016年6月29日 0:30
收件人: user
主题: Re: ignite group indexing not work problem
Hi,
I've tried the provided sample and found what instead of using oId_fNum_num
index H2 engine prefers oId_fNum_date,
thus preventing condition on num field to use index.
I think it's incorrect
Hi,
I've tried the provided sample and found what instead of using oId_fNum_num
index H2 engine prefers oId_fNum_date,
thus preventing condition on num field to use index.
I think it's incorrect behavior.
Could you disable oId_fNum_date, execute the query again and provide me
with the query
Hi there,
My ignite in-memory sql query is very slow. Anyone can help me to figure out
what was wrong?
I am using group indexing to speed up in-memory sql queries. I notice that my
sql query took 2274ms (data set size: 10Million, return result:1).
My query is executed as:
String qryStr =
