Hui, Steven [ICG-IT] would like to recall the message, "Enquiry of Long running
query and Timeout".
Yes, thats exactly what we need.
Thanx.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
The most useful information here is the plan that the RDBMS uses.
Is it possible to share it?
I suppose that using of either the IDX_ORG_MEDP_DRUG index or the
IDX_DRUG_ID index is not absolutely correct.
My bet is an index on (DRUG_ID, ORG_ID) could help here but it's to be
checked.
And it'
Please check you followed all standard recommendations summarized on this
page:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/sql-tuning
Pay attention to the "Basic Considerations: GridGain vs RDBMS" section.
-
Denis
On Fri, Feb 21, 2020 at 3:45 AM breathem wrote:
> Hello,
>
Hello!
Our current optimizer is not very smart. If you found an USE INDEX which
allows your query to run sufficiently fast, my recommendation is to just
use it.
Regards,
--
Ilya Kasnacheev
пт, 21 февр. 2020 г. в 14:45, breathem :
> Hello,
> We have two tables LD (8 000 000 rows) and DRUGS (13
Hello,
We have two tables LD (8 000 000 rows) and DRUGS (130 000 rows).
Following query is executed ~7 minutes that is significantly longer then in
RDBMS (~1,5 sec):
select d.drug_id, d.drug_name, ld.price
from drugs d
left outer join ld on d.drug_id = ld.drug_id and ld.org_id = 264;
Explain for q
