[
https://issues.apache.org/jira/browse/IMPALA-8072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-8072:
----------------------------------
Description:
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.
was:
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 stop including those config files or at least include a more
reasonable set of default configs.
> 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
>
> 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
