-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Enable result validation for collect_list Spark function in the Fuzzer #9361
Enable result validation for collect_list Spark function in the Fuzzer #9361
Conversation
✅ Deploy Preview for meta-velox canceled.
|
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.
@liujiayi771 Thank you for improving test coverage for the new aggregate function.
@mbasmanova has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@mbasmanova merged this pull request in 3e702c7. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
facebookincubator#9361) Summary: In facebookincubator#9231, `collect_list` is added to the disable list of `duckQueryRunner`. However, this is unnecessary because DuckDB does not have an aggregate function named `collect_list`, hence it would not be compared against DuckDB. This setting is redundant. Other than this, the results verification of `collect_list` has been set to `nullptr`, so its results are not verified. But we can use a custom array verifier used by Presto's `array_agg` to check the results of itself. Pull Request resolved: facebookincubator#9361 Reviewed By: xiaoxmeng Differential Revision: D55744044 Pulled By: mbasmanova fbshipit-source-id: a1a94c58b2a01463261775d8b6e08b65fd986d29
In #9231,
collect_list
is added to the disable list ofduckQueryRunner
.However, this is unnecessary because DuckDB does not have an aggregate function
named
collect_list
, hence it would not be compared against DuckDB. Thissetting is redundant.
Other than this, the results verification of
collect_list
has been set tonullptr
, so its results are not verified. But we can use a custom arrayverifier used by Presto's
array_agg
to check the results of itself.