I suppose it can be made to be not incompatible, but with a non-newbie effort. The "||" is parsed as a CompoundPredicate today and we cannot decide at parse time whether "||" is used as OR or as CONCAT. So the easiest solution is to pick one variant and go with it.
Determining the variant later during compilation requires deeper changes. On Fri, Apr 13, 2018 at 9:55 AM, Tim Armstrong <tarmstr...@cloudera.com> wrote: > Why is it incompatible? > > > On Fri, Apr 13, 2018 at 9:05 AM, Alexander Behm <alex.b...@cloudera.com> > wrote: > > > IMPALA-452 is not a good candidate because it's an incompatible change, > > > > On Fri, Apr 13, 2018 at 9:00 AM, Tim Armstrong <tarmstr...@cloudera.com> > > wrote: > > > > > Here are a few JIRAs that might be good starters: > > > https://issues.apache.org/jira/browse/IMPALA-6844 (bug in builtin > > > function) > > > https://issues.apache.org/jira/browse/IMPALA-6393 (adding a small > > > improvement to impala-shell) > > > https://issues.apache.org/jira/browse/IMPALA-6234 (fixing a bug in > query > > > analysis) > > > https://issues.apache.org/jira/browse/IMPALA-452 (adding || as string > > > concat operator - a little more advanced) > > > > > > On Fri, Apr 13, 2018 at 7:07 AM, Jim Apple <jbap...@cloudera.com> > wrote: > > > > > > > I asked on 5610 if it's a duplicate with the ticket that > > > > https://gerrit.cloudera.org/c/9173 resolves. > > > > > > > > 5392 has two open patches: https://gerrit.cloudera.org/#/c/10032/ > and > > > > https://gerrit.cloudera.org/#/c/10040/. I have encouraged the > authors > > to > > > > work together or to pick one and go with it. > > > > > > > > On Fri, Apr 13, 2018 at 12:21 AM, Gabor Kaszab < > > gaborkas...@cloudera.com > > > > > > > > wrote: > > > > > > > > > I see. > > > > > If those are in progress, can someone be assigned to their Jira and > > the > > > > > status of them be set to "In Progress" to avoid any > misunderstanding? > > > > > > > > > > Gabor > > > > > > > > > > On Fri, Apr 13, 2018 at 9:14 AM, Fredy Wijaya < > fwij...@cloudera.com> > > > > > wrote: > > > > > > > > > > > Unfortunately those two tickets are not available either. > > > > > > > > > > > > https://issues.apache.org/jira/browse/IMPALA-5392 (currently in > > > > progress > > > > > > https://gerrit.cloudera.org/c/10032/) > > > > > > https://issues.apache.org/jira/browse/IMPALA-5610 (has already > > been > > > > > > completed in https://gerrit.cloudera.org/c/9173) > > > > > > > > > > > > We have tickets that are labelled newbie: https://issues.apache. > > > > > > org/jira/browse/IMPALA-6844?jql=project%20%3D%20IMPALA% > > > > > > 20AND%20labels%20%3D%20newbie%20AND%20assignee%20in%20(EMPTY) > for > > > > anyone > > > > > > to > > > > > > grab. > > > > > > ------------------------------ > > > > > > > > > > > > On Fri, Apr 13, 2018 at 1:50 AM, Gabor Kaszab < > > > > gaborkas...@cloudera.com> > > > > > > wrote: > > > > > > > > > > > > > Hey, > > > > > > > > > > > > > > As I see that task just got an assignee (abhishek at > > > sigmoidanalytics > > > > > dot > > > > > > > com) yesterday so I'm afraid it is not free to pick up anymore. > > > > > > > > > > > > > > I found 2 Impala related tasks from helpwanted.apache.org that > > are > > > > not > > > > > > > assigned to anyone: > > > > > > > - https://issues.apache.org/jira/browse/IMPALA-5392 > > > > > > > - https://issues.apache.org/jira/browse/IMPALA-5610 > > > > > > > Are you interested in any of them? > > > > > > > > > > > > > > Jim, As I see the issues with an assignee still appear in the > > > > > > > helpwanted.apache.org search list (these are still in Open > > state, > > > > > > though). > > > > > > > Is this intentional? Shouldn't those disappear once the issue > > gets > > > an > > > > > > > assignee? > > > > > > > > > > > > > > Cheers, > > > > > > > Gabor > > > > > > > > > > > > > > > > > > > > > On Fri, Apr 13, 2018 at 8:02 AM, Kayli Jiang < > > > kayliji...@icloud.com> > > > > > > > wrote: > > > > > > > > > > > > > > > I would like to help out with the task listed at > > > > > > > > https://helpwanted.apache.org/task.html?544bf69e > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
