[jira] [Commented] (IMPALA-8072) Clean up config files in docker containers
[ https://issues.apache.org/jira/browse/IMPALA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16839844#comment-16839844 ] ASF subversion and git services commented on IMPALA-8072: - Commit d12675af59f2ac74db4fae09d41b720bfd72fe4b in impala's branch refs/heads/master from Tim Armstrong [ https://gitbox.apache.org/repos/asf?p=impala.git;h=d12675a ] IMPALA-8072: addendum: don't require fe rebuild for config Previously config changes wouldn't be picked up by containers until maven copied the files from fe/src/test/resources to fe/target/test-classes. This makes it more convenient - after running ./bin/create-test-configuration.sh new configs are picked up by any newly-run containers. Change-Id: I18f9f90667b1d16cf97d3e3f9fac400980d5b733 Reviewed-on: http://gerrit.cloudera.org:8080/13288 Reviewed-by: Impala Public Jenkins Tested-by: Impala Public Jenkins > Clean up config files in docker containers > -- > > Key: IMPALA-8072 > URL: https://issues.apache.org/jira/browse/IMPALA-8072 > Project: IMPALA > Issue Type: Sub-task > Components: Infrastructure >Affects Versions: Impala 3.2.0 >Reporter: Tim Armstrong >Assignee: Tim Armstrong >Priority: Major > Labels: docker > Fix For: Impala 3.3.0 > > > Currently the docker containers include a bunch of config files copied > indiscriminately from the dev environment. Mostly these aren't valid for a > production container and it's expected that the real config files will be > mounted at /opt/impala/conf. > We should instead include a more reasonable set of default configs (e.g. for > admission control), plus placeholders for other config files that may need to > be overridden with site-specific configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Commented] (IMPALA-8072) Clean up config files in docker containers
[ https://issues.apache.org/jira/browse/IMPALA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16826274#comment-16826274 ] ASF subversion and git services commented on IMPALA-8072: - Commit b66ac16375d6763e5b5a0128d66e73835dcef904 in impala's branch refs/heads/master from Tim Armstrong [ https://gitbox.apache.org/repos/asf?p=impala.git;h=b66ac16 ] IMPALA-8072: remove junk configs from containers The docker containers currently have minicluster configs baked into them. This is not necessary any more since the /opt/impala/conf directory is mounted to point at the up-to-date configs, so there's no reason to include configs in the container. Testing: Confirmed that I could build containers, start up a minicluster and run queries. Change-Id: I6d77f79620514187a5c45483e9051bd8c40dfc9e Reviewed-on: http://gerrit.cloudera.org:8080/13104 Reviewed-by: Impala Public Jenkins Tested-by: Impala Public Jenkins > Clean up config files in docker containers > -- > > Key: IMPALA-8072 > URL: https://issues.apache.org/jira/browse/IMPALA-8072 > Project: IMPALA > Issue Type: Sub-task > Components: Infrastructure >Affects Versions: Impala 3.2.0 >Reporter: Tim Armstrong >Assignee: Tim Armstrong >Priority: Major > Labels: docker > Fix For: Impala 3.3.0 > > > Currently the docker containers include a bunch of config files copied > indiscriminately from the dev environment. Mostly these aren't valid for a > production container and it's expected that the real config files will be > mounted at /opt/impala/conf. > We should instead include a more reasonable set of default configs (e.g. for > admission control), plus placeholders for other config files that may need to > be overridden with site-specific configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
