You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Fredy Wijaya (JIRA)" <ji...@apache.org> on 2019/03/27 20:08:00 UTC

[jira] [Resolved] (IMPALA-8340) IMPALA-8337 adds configparser dependency which isn't always available where impala-shell is installed

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

Fredy Wijaya resolved IMPALA-8340.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> IMPALA-8337 adds configparser dependency which isn't always available where impala-shell is installed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-8340
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8340
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Clients
>            Reporter: Tim Armstrong
>            Assignee: Fredy Wijaya
>            Priority: Blocker
>              Labels: broken-build
>             Fix For: Impala 3.3.0
>
>
> This may break other things. I've seen some failures on systems like this:
> {noformat}
> Command exited with code: 1
> Command output: Traceback (most recent call last):
>   File "/usr/lib/impala-shell/impala_shell.py", line 42, in <module>
>     from option_parser import get_option_parser, get_config_from_file
>   File "/usr/lib/impala-shell/lib/option_parser.py", line 30, in <module>
>     import configparser
> ImportError: No module named configparser
> {noformat}
> I think we would need to add configparser to shell/ext-py so that it's packaged with the rest of the shell stuff. I'm not sure if there are other steps too



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