[ https://issues.apache.org/jira/browse/IMPALA-12814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe McDonnell reassigned IMPALA-12814: -------------------------------------- Assignee: Joe McDonnell > VERIFY_IS_NOT_IN does not work with row_regex: > ---------------------------------------------- > > Key: IMPALA-12814 > URL: https://issues.apache.org/jira/browse/IMPALA-12814 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure > Affects Versions: Impala 4.3.0 > Reporter: Joe McDonnell > Assignee: Joe McDonnell > Priority: Major > > When testing some changes that would add content to explain plan, I see that > VERIFY_IS_NOT_IN does not work with row_regex. Here is a trivial case that > should always fail: > {noformat} > ---- RESULTS: VERIFY_IS_NOT_IN > row_regex:.*{noformat} > It does not fail. It looks like it is doing set logic without paying > attention to row_regex: > {noformat} > def verify_query_result_is_not_in(expected_results, actual_results): > assert_args_not_none(expected_results, actual_results) > expected_set = set(map(unicode, expected_results.rows)) > actual_set = set(map(unicode, actual_results.rows)) > assert expected_set.isdisjoint(actual_set){noformat} > [https://github.com/apache/impala/blob/b15d6dc2e7df05392a1daa4bc1b3da9ca31a583b/tests/common/test_result_verifier.py#L298-L302] > It looks like some existing test cases use it this way. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org