[
https://issues.apache.org/jira/browse/IMPALA-11689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18050883#comment-18050883
]
Csaba Ringhofer commented on IMPALA-11689:
------------------------------------------
Just checked if this ticket is still valid after IMPALA-13694 which adds reset
to client configurations after tests. It seems that interfering is still
possible with other tests, as self.execute_query("SET
RUNTIME_FILTER_MODE=GLOBAL") will change the session options on server side
instead of the conf overlay in the client.
A simple way to fix this would be to rewrite this SET statements to
client.set_configuration_option, or to detect SET in execute_query and change
the client config instead of doing an RPC to the server.
> Some e2e tests are not independent of each other
> ------------------------------------------------
>
> Key: IMPALA-11689
> URL: https://issues.apache.org/jira/browse/IMPALA-11689
> Project: IMPALA
> Issue Type: Bug
> Reporter: Zoltán Borók-Nagy
> Priority: Major
> Labels: newbie, ramp-up
>
> There are some tests that have side-effects during test execution.
> E.g. they set query options on the Impala client of the test suite:
> self.execute_query("SET RUNTIME_FILTER_MODE=GLOBAL")
> https://github.com/apache/impala/blob/8e350d0a8a7c95810c7704c8a5264a60daed783d/tests/query_test/test_runtime_filters.py#L138
> Tests shouldn't have such side-effects. Instead of setting a query option for
> the impala client of the whole test suite, they should create a private
> client for them. Or modify the test vector's 'exec_option' if possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
