[
https://issues.apache.org/jira/browse/IMPALA-9618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17079499#comment-17079499
]
ASF subversion and git services commented on IMPALA-9618:
---------------------------------------------------------
Commit 5989900ae81a98d6977bdd60f2281da47e9f69b7 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=5989900 ]
IMPALA-9618: fix some usability issues with dev env
Automatically assume IMPALA_HOME is the source directory
in a couple of places.
Delete the cache_tables.py script and MINI_DFS_BASE_DATA_DIR
config var which had both bit-rotted and were unused.
Allow setting IMPALA_CLUSTER_NODES_DIR to put the minicluster
nodes, most important the data, in a different location, e.g.
on a different filesystem.
Testing:
I set up a dev environment using this code and was able to
load data and run some tests.
Change-Id: Ibd8b42a6d045d73e3ea29015aa6ccbbde278eec7
Reviewed-on: http://gerrit.cloudera.org:8080/15687
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Usability issues with dev env setup.
> ------------------------------------
>
> Key: IMPALA-9618
> URL: https://issues.apache.org/jira/browse/IMPALA-9618
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> bootstrap_system.sh should be able to auto-detect IMPALA_HOME. The only
> reasonable default for IMPALA_HOME is the repository that the script is being
> run from. We should detect that, instead of defaulting to ~/Impala, which
> results in a weird error if you checked out Impala somewhere else.
> We should be able to put the minicluster data directory in a different place
> from the source checkout, e.g. if you want to put it on a different disk.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
