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

Tim Armstrong resolved IMPALA-4075.
-----------------------------------
    Resolution: Won't Fix

> Test kudu connection failed due to env KUDU_IS_SUPPORTED is set to false
> ------------------------------------------------------------------------
>
>                 Key: IMPALA-4075
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4075
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.7.0
>         Environment: LSB Version:     
> :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch
> Distributor ID:       CentOS
> Description:  CentOS release 6.7 (Final)
> Release:      6.7
> Codename:     Final
>            Reporter: hewenting
>            Assignee: hewenting
>            Priority: Minor
>              Labels: kudu, test
>
> Execute tests in file tests/conftest.py fail, as below shows:
> {noformat}
> Traceback (most recent call last):
>   File "conftest.py", line 21, in <module>
>     from kudu import connect as kudu_connect
> ImportError: No module named kudu
> {noformat}
> we should check environment variable "KUDU_IS_SUPPORTED" first.
> Only if this var is set to true, we can use "from kudu import connect as 
> kudu_connect".
> *Workaround*
> * temporarily export KUDU_IS_SUPPORTED=true
> * run bin/bootstrap_toolchain.py
> * set KUDU_IS_SUPPORTED back to original value
> * tests should run now



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

Reply via email to