You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2025/03/25 21:20:00 UTC

[jira] [Resolved] (IMPALA-13747) unique_database fixture may taint ImpalaTestSuite.client

     [ https://issues.apache.org/jira/browse/IMPALA-13747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Riza Suminto resolved IMPALA-13747.
-----------------------------------
    Fix Version/s: Impala 5.0.0
                   Impala 4.5.0
       Resolution: Fixed

> unique_database fixture may taint ImpalaTestSuite.client
> --------------------------------------------------------
>
>                 Key: IMPALA-13747
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13747
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Major
>             Fix For: Impala 5.0.0, Impala 4.5.0
>
>
> Just like IMPALA-13634 bug, unique_database fixture may taint ImpalaTestSuite.client by setting 'sync_ddl=True' option, but never cleaning it up for test method usage.
> [https://github.com/apache/impala/blob/856741b1e8371b983da10f23a166f19aac71f1f8/tests/conftest.py#L410-L412] 
> unique_database fixture should use a fresh Impala client for both creating and dropping database.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)