-
Notifications
You must be signed in to change notification settings - Fork 52
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
agg enable corr covar_pop and covar_samp #147
Conversation
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
* Enable corr covar_pop and covar_samp in aggregate. * Adjust the accuracy to align with Spark.
Would you create a pr to upstream this change to velox community when you are free? @liujiayi771 |
OK. I will discuss this order of calculation with meta. Because the current modification is to meet the calculation results consistent with spark, but it may lead to inconsistent results with presto, we need to see how to solve it better. |
Thank you very much to explain the root cause. |
I will try to fix this on our side without change Velox codes. |
We should import Epsilon Compare for floating-point value. |
Hi @liujiayi771, do you suggest importing it in Gluten CI? |
Hi, @rui-mo , maybe we can allow a certain error for floating-point numbers when comparing gluten results with vanilla spark. This is what velox does when comparing results with duckdb. |
@liujiayi771 That makes sense to me. We can add some precision tolerance when comparing floats. |
enable corr, covar_pop and covar_samp.