[ https://issues.apache.org/jira/browse/IMPALA-8062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Apple resolved IMPALA-8062. ------------------------------- Resolution: Fixed https://gitbox.apache.org/repos/asf?p=impala.git;a=commit;h=fa672909c868f76aa50e9fb756114c32daaf6d9b IMPALA-8062: Call impala-config in single_node_perf_run This wraps most shell calls in single_node_perf_run.py with a bash shell that first sources impala-config.sh, to make sure environment variables are set properly. Change-Id: Ic7c1b77906a975c37f3b51a0f900ed3536b398ba Reviewed-on: http://gerrit.cloudera.org:8080/12277 > single_node_perf_run.py doesn't re-source impala-config.sh on different > branches > -------------------------------------------------------------------------------- > > Key: IMPALA-8062 > URL: https://issues.apache.org/jira/browse/IMPALA-8062 > Project: IMPALA > Issue Type: Bug > Components: Infrastructure > Reporter: Tim Armstrong > Assignee: Jim Apple > Priority: Major > > There are some cases when impala-config.sh needs to be re-sourced when > switching branches. E.g. for the case when run-workload.py starts the > cluster, some variables are picked up from the environment. > It would probably be helpful to have a "run-with-impala-config.sh" script > that runs a command after sourcing impala-config.sh -- This message was sent by Atlassian JIRA (v7.6.3#76005)