-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[Data] - Fix test_expression_evaluator #57848
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
[Data] - Fix test_expression_evaluator #57848
Conversation
Signed-off-by: Goutam <goutam@anyscale.com>
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.
Code Review
This pull request addresses a bug in the expression evaluator concerning the is_in
operation. The changes correctly replace the erroneous .is_in()
method call on PyArrow expression objects with the appropriate pyarrow.compute.is_in
function. This correction is applied to both the in
operator within comparison expressions and the is_in
function call handler. The fix is accurate and effectively resolves the described issue.
|
||
comparators = [self.visit(comp) for comp in node.comparators] | ||
|
||
op = node.ops[0] |
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.
Can you remove test_expression_evaluator.py
from semgrep.yml
, and also add the pytest.main
to the bottom of test_expression_evaluator.py
?
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.
Done
Description
The old expression evaluator did not correctly handle
is_in
which failed tests intest_expression_evaluator
Related issues
Fixes #57820
Additional information