hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-19882) Fix QTestUtil session lifecycle
Date Mon, 18 Jun 2018 08:50:00 GMT

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

Zoltan Haindrich updated HIVE-19882:
------------------------------------
    Description: 
there are a number of strange come and go failing tests; it was always strange to me that
qtestutil cleans up at some questionable points - this seems to be leading to executing some
commands with the previous qfiles session...

ideally the session/etc should start/reused in {{before}}
and it should be closed in {{after}}

seems like configuration is handled probably incorrectly; saving the conf after initialization
- and restoring it for a new session should ensure consistency

  was:

there are a number of strange come and go failing tests; it was always strange to me that
qtestutil cleans up at some questionable points - this seems to be leading to executing some
commands with the previous qfiles session...

ideally the session/etc should start/reused in {{before}}
and it should be closed in {{after}}


> Fix QTestUtil session lifecycle
> -------------------------------
>
>                 Key: HIVE-19882
>                 URL: https://issues.apache.org/jira/browse/HIVE-19882
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Tests
>            Reporter: Zoltan Haindrich
>            Assignee: Zoltan Haindrich
>            Priority: Major
>         Attachments: HIVE-19882.01.patch, HIVE-19882.02.patch, HIVE-19882.03.patch
>
>
> there are a number of strange come and go failing tests; it was always strange to me
that qtestutil cleans up at some questionable points - this seems to be leading to executing
some commands with the previous qfiles session...
> ideally the session/etc should start/reused in {{before}}
> and it should be closed in {{after}}
> seems like configuration is handled probably incorrectly; saving the conf after initialization
- and restoring it for a new session should ensure consistency



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message