-
Notifications
You must be signed in to change notification settings - Fork 72
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
Add support for VALUES query #1038
base: main
Are you sure you want to change the base?
Conversation
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## main #1038 +/- ##
==========================================
+ Coverage 79.08% 81.54% +2.45%
==========================================
Files 78 78
Lines 4395 4395
Branches 797 797
==========================================
+ Hits 3476 3584 +108
+ Misses 743 628 -115
- Partials 176 183 +7
... and 3 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
Cool! Thanks for this addition Ayush. All the changes look sound to me
@charlesbluca since this is also one of those cases which would benefit from cpu/gpu handling does it make sense to followup on this once #1117 is complete? |
Yeah that makes sense - also okay with merging this in as is and iterating on it in my PR if we need VALUES implemented on CPU to unblock something |
Fixes #1013
Initial attempt at supporting the Values query.
Currently limited to creating the result on cpu dataframes only but eventually plan on extending to GPU frames via some common config.