[jira] [Created] (CALCITE-4888) Unexpected `RexNode` when call `RelBuilder.in` to create an `IN` predicate with a list of varchar literals which have different length

JING ZHANG created CALCITE-4888: --- Summary: Unexpected `RexNode` when call `RelBuilder.in` to create an `IN` predicate with a list of varchar literals which have different length Key: CALCITE-4888 URL: https

Re: VARCHAR literals

Just ran into CALCITE-2321 in Beam, this is something we would be interested in as well. Andrew On Tue, Sep 11, 2018 at 7:47 AM Piotr Nowojski wrote: > Thanks! We will look into it. If we decide to go this path we will create > a JIRA ticket for this. > > Piotrek > > > On 10 Sep 2018, at

Re: VARCHAR literals

Thanks! We will look into it. If we decide to go this path we will create a JIRA ticket for this. Piotrek > On 10 Sep 2018, at 19:12, Julian Hyde wrote: > > Yes, as long as it is fully tested and documented. This is not a one line > fix. It’s quite a major feature, and if it’s not done

Re: VARCHAR literals

Yes, as long as it is fully tested and documented. This is not a one line fix. It’s quite a major feature, and if it’s not done properly Calcite will be picking up the pieces for years. Julian > On Sep 10, 2018, at 1:26 AM, Piotr Nowojski wrote: > > Julian, would you be ok if we provided a

Re: VARCHAR literals

Julian, would you be ok if we provided a contribution containing a configurable switch for string literal type? Piotrek > On 6 Sep 2018, at 20:47, Piotr Nowojski wrote: > > We know about this switch. Unfortunately it only solves/hides one of the > problems. > >> On 6 Sep 2018, at 20:02,

Re: VARCHAR literals

We know about this switch. Unfortunately it only solves/hides one of the problems. > On 6 Sep 2018, at 20:02, Julian Hyde wrote: > > Does https://issues.apache.org/jira/browse/CALCITE-2321 > help? > > >> On Sep 6, 2018, at 4:03 AM, Piotr

Re: VARCHAR literals

Does https://issues.apache.org/jira/browse/CALCITE-2321 help? > On Sep 6, 2018, at 4:03 AM, Piotr Nowojski wrote: > > Hi, > > We have small problem with CHAR type in Flink. Officially we do not support > it and all input/output columns

VARCHAR literals

Hi, We have small problem with CHAR type in Flink. Officially we do not support it and all input/output columns are of type VARCHAR. Because of that, nobody has ever thought about CHAR semantic (for example correctly handling padding in comparisons or other functions). However this collides