Re: Contribution of IN operator handling
Convert SqlInOperator to In-Expression :
Related. full table scans and subQueryThreshold.
On Tue, Nov 20, 2018 at 12:08 PM Julian Hyde <jhyde@xxxxxxxxxx> 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?
> > On Nov 20, 2018, at 8:23 AM, Mykola Zerniuk <mykola.zerniuk@xxxxxxxx.INVALID>
> > 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:
> > 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