You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "David Knupp (Jira)" <ji...@apache.org> on 2020/03/12 22:30:00 UTC

[jira] [Updated] (IMPALA-9489) Setup impala-shell.sh env separately, and use thrift-0.11.0 by default.

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

David Knupp updated IMPALA-9489:
--------------------------------
    Summary: Setup impala-shell.sh env separately, and use thrift-0.11.0 by default.  (was: Have impala-python env and impala-shell use available thrift-0.11.0 files)

> Setup impala-shell.sh env separately, and use thrift-0.11.0 by default.
> -----------------------------------------------------------------------
>
>                 Key: IMPALA-9489
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9489
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Infrastructure
>    Affects Versions: Impala 3.4.0
>            Reporter: David Knupp
>            Assignee: David Knupp
>            Priority: Major
>
> Apparently, we can't simply kick thrift-0.9.3 to the curb. Our build needs some attention before that can happen, per IMPALA-7825, and also conversation I had with [~stakiar_impala_496e]. 
> However, with IMPALA-7924 resolved, we do have access to thrift-0.11.0 python files, and we should use those by default. It turns out that being stuck with thrift-0.9.3 is a major impediment to achieving python 3 compatibility for our python stack.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org