-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support parsing SQL strings to Exprs #10995
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks great -- thank you so much @xinlifoobar
I have some suggestions that could make the examples / code easier to read, but they could be done as follow on PRs too. I think the code is really nice. Well done 🏆
cc @Omega359 @jiacai2050 @devinjdangelo @backkem and @Jefffrey as you expressed interest in #8736
4924acb
to
578d198
Compare
578d198
to
b220130
Compare
b220130
to
6035703
Compare
Sorry for the confusions... I merged a bad local main and messed up the histories. Fixed up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great -- thanks again @xinlifoobar
* Draft parse_sql * Allow stirng pass * Complete sql to expr support * Add examples * Add unit tests * Fix format * Remove async for trival operation and add parquet demo * Fix comments * fix comments * fix comments * Fix doc link
Which issue does this PR close?
Closes #8736
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?