Convert SqlInOperator to In-Expression : https://issues.apache.org/jira/browse/CALCITE-2630
Related. full table scans and subQueryThreshold. https://lists.apache.org/thread.html/1a25c956262633f8ef0d224ed76400761f6797c494a21796579eb4f2@%3Cdev.calcite.apache.org%3E On Tue, Nov 20, 2018 at 12:08 PM Julian Hyde <[email protected]> wrote: > I recall contributing to some other conversations about large IN lists > over the past few months. Before we jump into a discussion, can you locate > those threads? Also, if there is not a JIRA case, can you please create one? > > Julian > > > On Nov 20, 2018, at 8:23 AM, Mykola Zerniuk > > <[email protected]> > wrote: > > > > Dear Calcite Administrators, > > > > my name is Mykola, software engineer from Ukraine. > > > > I had an issue with Calcite IN operator handling. > > > > Here is my previous email to you: > > > https://mail-archives.apache.org/mod_mbox/calcite-dev/201810.mbox/%3CCAL4PLbiBh1HoP0w_5ScJ1Nnxq%2BNYGP2LO2usxg_17Gs1mYgttA%40mail.gmail.com%3E > > > > It is really important to us to have an option to left IN operator "as > > is" and do not do any conversions. I implemented it a while ago at my > > local, and it successfully works in our project. > > > > Our team would be happy to have your review and contribute it to Calcite. > > > > If you have no objections may i create a work item in Jira? I am > > following these steps: > > https://calcite.apache.org/develop/#contributing > > > > Thanks a lot, > > Mykola > >
