Hi Mykola,
In the previous discussion that you cited above, people lean towards the
option of adding a new rule and not really changing the converter. From a
quick look, it seems that Zoltan also shared some code for transforming ORs
back to IN which you may be able to reuse/extend as you like.
You should be able to work around this by setting inSubQueryThreshold to
Integer.MAX_VALUE..
--
Michael Mior
mm...@apache.org
Le mer. 10 oct. 2018 à 10:04, Mykola Zerniuk
a écrit :
> Hello calcite devs!
> My name is Mykola, a am software engineer. We actively use calcite
> framework in our
Hello calcite devs!
My name is Mykola, a am software engineer. We actively use calcite
framework in our project, and recently faced with next issue:
Some of SQL has huge IN list (more than 1500). Right now Calcite's SQL
parser replaces INs with ORs or sub-queries depending on the
