-
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
Fix FunctionType::equivalent #6952
Conversation
✅ Deploy Preview for meta-velox canceled.
|
@xiaoxmeng Hi Xiaoxuan, could you please help review this PR? I found this issue when I tried to add UT at #6950. Thanks a lot. |
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.
@duanmeng LGTM. Thanks for the fix!
@xiaoxmeng has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@xiaoxmeng merged this pull request in 417e43f. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Summary: `FunctionType::equivalent` only works for `ScalarType` arguments, it returns wrong results when arguments are `ComplexType`, say `FUNCTION<ARRAY<BIGINT>, BOOLEAN>` vs. `FUNCTION<ARRAY<BIGINT>, BOOLEAN>` would return false if using this API. Pull Request resolved: facebookincubator#6952 Reviewed By: bikramSingh91 Differential Revision: D50072758 Pulled By: xiaoxmeng fbshipit-source-id: 04ad1dbe887553658e1c5d67a3132bea0b3c0f27
FunctionType::equivalent
only works forScalarType
arguments,it returns wrong results when arguments are
ComplexType
, sayFUNCTION<ARRAY<BIGINT>, BOOLEAN>
vs.FUNCTION<ARRAY<BIGINT>, BOOLEAN>
would return false if using this API.