Re: Parser for expressions

2022-10-13 Thread Sasha Krassovsky
quot; -> "arrow >>>>>>>>> expression". >>>>>>>>> >>>>>>>>> Since no text format exists for Substrait I think that Substrait >> does >>>>>>>>> not currently solve this problem

Re: Parser for expressions

2022-10-12 Thread Joris Van den Bossche
to parse but > lacks > > >>>>>> some of the shortcut conveniences (e.g. implicit types for > literals, > > >>>>>> support for common infix operators (+, -, /, ...)). > > >>>>>> > > >>>>>> Bo

Re: Parser for expressions

2022-10-11 Thread Weston Pace
gt; >>>>>> Compared with [1] I think this proposal is simpler to parse but lacks > >>>>>> some of the shortcut conveniences (e.g. implicit types for literals, > >>>>>> support for common infix operators (+, -, /, ...)). > >>>>>> >

Re: Parser for expressions

2022-10-10 Thread Antoine Pitrou
t;> Sent: Wednesday, October 5, 2022 11:29 AM To: dev@arrow.apache.org <mailto:dev@arrow.apache.org> Subject: Parser for expressions External Email: Use caution with links and attachments Hi everyone, I’ve noticed on the mailing list a few times people asking for a more convenient

Re: Parser for expressions

2022-10-10 Thread Sasha Krassovsky
t;> I'm +0.5 on this change. I worry a bit about having (eventually) >>>>> three different syntaxes. However, at the moment we have zero. >>>>> >>>>> [1] https://lists.apache.org/thread/0oyns380hgzvl0y8kwgqoo4fp7ntt3bn >>>>> >&

Re: Parser for expressions

2022-10-09 Thread Jin Shang
apache.org/thread/0oyns380hgzvl0y8kwgqoo4fp7ntt3bn >>>> >>>>> On Wed, Oct 5, 2022 at 1:55 PM Sasha Krassovsky >>>>> wrote: >>>>> >>>>> Hi David, >>>>> Could you elaborate on which part of my proposal over

Re: Parser for expressions

2022-10-07 Thread Sasha Krassovsky
the lines of >>>> >>>> Expression e = Expression::FromString(“(add !.a $int32:1)”); >>>> >>>> in the code. >>>> >>>> Sasha >>>> >>>>>> On Oct 5, 2022, at 1:35 PM, Lee, David >> wrote: >

Re: Parser for expressions

2022-10-06 Thread Jin Shang
gt; > >> Expression e = Expression::FromString(“(add !.a $int32:1)”); > >> > >> in the code. > >> > >> Sasha > >> > >>>> On Oct 5, 2022, at 1:35 PM, Lee, David > wrote: > >>> > >>> I believe this is

Re: Parser for expressions

2022-10-06 Thread Sasha Krassovsky
PM, Lee, David >>>> wrote: >>> >>> I believe this is what substrait.io <http://substrait.io/> is trying to >>> accomplish.. >>> >>> Here's some additional info: >>> https://substrait.io/ <https://substrait.io/&g

Re: Parser for expressions

2022-10-06 Thread Weston Pace
o/ <https://substrait.io/> > > > > https://www.youtube.com/watch?v=5JjaB7p3Sjk > > <https://www.youtube.com/watch?v=5JjaB7p3Sjk> > > > > -Original Message----- > > From: Sasha Krassovsky > <mailto:krassovskysa...@gmail.com>> > &g

Re: Parser for expressions

2022-10-05 Thread Sasha Krassovsky
> <https://www.youtube.com/watch?v=5JjaB7p3Sjk> > > -Original Message- > From: Sasha Krassovsky <mailto:krassovskysa...@gmail.com>> > Sent: Wednesday, October 5, 2022 11:29 AM > To: dev@arrow.apache.org <mailto:dev@arrow.apache.org> > Subject: Parser for expression

RE: Parser for expressions

2022-10-05 Thread Lee, David
arser for expressions External Email: Use caution with links and attachments Hi everyone, I’ve noticed on the mailing list a few times people asking for a more convenient way to construct an Expression, namely using a string of some sort. I’ve found myself wishing for something like this too

Parser for expressions

2022-10-05 Thread Sasha Krassovsky
Hi everyone, I’ve noticed on the mailing list a few times people asking for a more convenient way to construct an Expression, namely using a string of some sort. I’ve found myself wishing for something like this too when constructing ExecPlans, and so I’ve gone ahead and implemented a parser [0]