[
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: Setup impala-shell.sh env separately, and use thrift-0.11.0 by
default.)
> 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-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
