This message was deleted.
# general
s
This message was deleted.
l
I am not completely sure, but afaik MSQ can’t plan righty joins. Can you post the sql plans for both the engines. Also, for a simple select, MSQ is bound to be slower because MSQ launches tasks, reads segments and then performs the queries.
b
Is it MSQ? The SQL and the explain output would help, to give a +1 to what Laksh said.
a
I did explain on sql Query and the json query I.e plan output I used to do json query answered in less than a second
b
What is the SQL query? (Wild stab, does it have a long IN list?) If you post the query, that would help.
a
Yes it has
I will get the query from the team
b
I had a hunch, sounded like the planning step (SQL -> native) takes a long time. You can try setting
"inSubQueryThreshold": 0"
in the query context. I found this helped in the past (eg here).